-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ys_col_note #120
ys_col_note #120
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. I had one suggestion to for the code.
To answer you questions above:
- I would default to no units. No huge preference but my thinking was if I use this selectively for a subset of longer column definitions then I would already have chosen to either add the units to the table directly (in which case, no need to duplicate them) or I would have chosen not to add them (in which case it would be odd to only add it to a few in the footer). Having said that, if someone is using this to explain all abbreviations, I would hate them to forget the units... maybe that would be a better argument to keep them?
- I would suggest we don't default to title case - you don't use it when explaining abbreviations used in the canned pmtables functions and I could see this being used frequently with those tables. It would look more odd to see a mix of cases used
- Happy to go with the convenience of a single string but I like that you added the flexibility in there. I can see someone wanting a series of abbreviations from the spec and plus one/two additional ones they want to squeeze in somewhere.
Co-authored-by: KatherineKayMRG <42553148+KatherineKayMRG@users.noreply.github.com>
@KatherineKayMRG Thanks for reviewing; I believe everything is up to date based on your review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @kylebaron - Looks great!
Awesome! |
Summary
yspec
object and create a column definition stringTRUE
?TRUE
?TRUE
@KatherineKayMRG I simplified this quite a bit based on initial prototyping. I felt like it wasn't that obvious what columns were going to come back in the note and that it was reasonable to just ask to name the columns to appear. This would (I think) also allow user to enforce an order which might be nice.
Example
Created on 2022-03-17 by the reprex package (v2.0.1)