Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
introduce teal_data class #178
introduce teal_data class #178
Changes from 64 commits
e622149
9827de3
2daf83a
bef092f
3f723f3
5e3c0cb
7429b55
e964b95
1b1ebc6
3f37efe
212806c
7d9e2b0
7edaf2a
b30029b
2248740
1ca4cb1
6504197
d067b93
56a7b2d
f3876df
c407adf
5443613
48e0f3b
6b46e4c
2c9da20
fc853ad
b56ee4e
4ff57d0
32adc7c
7300049
4900aef
f7204f4
67f96e4
801bc72
7118d58
c461980
75095ec
36d4544
2fb8a39
0e26f43
e62f3a7
2680837
4f26d55
75f0890
2c0e3f7
7cb1986
55d0dbc
9b3c303
985d06c
0bb43d8
1720d43
b3cea7d
67dea47
d4a8a5d
d869de6
b944347
2485c0b
b7d7038
095a9be
1a08953
9fb959d
904998e
d926022
8a7dbc4
a3ebc25
d8be870
8348640
8f3b812
bb6e0ff
18e1055
0e727c7
3f93eae
cebb61f
4a0aeb9
f3de72c
996d080
4c03c22
5936220
88fc42d
2355695
bfa77c1
9c73c29
a1e092c
2fdfeed
4dd52bd
f10d94a
ffa1e00
7771928
d7b3bcd
3bc4e6b
0dc21e0
5ba4f99
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
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.
should specify when
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.
Use code-push in examples? (empty
cdisc_data
followed bywithin
)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.
Do we want to support "dynamic dots"?
I am thinking here about re-collecting dots with
rlang:: dots_list
which has in-built support for names assertions and others. This could be important from error message consistency reasons.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.
Actually I think that this could be a very neat feature implemented at relatively low cost.
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.
Yes, but at this moment this list could be named (new approach) and unnamed (old approach). So I can't just assert directly when obtaining
...
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.
You would have to collect dots twice
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.
Three times actually, because logical condition is based on output from
...
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.
ok how about this:
Then after we hard deprecate old approach it would be just this:
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.
If you introduce a new method please check for possible replacement of old method for consistency reasons
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.
This feels a little aggressive. How about: please see methods to interact with class' slots.
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.
I let you suggest the whole phrase. I don't agree with idea of writing documentation and commands with too polite language (what is too polite I don't know either as it depends who you talking with). I think it should be clear what should be done and what is not allowed for users.
I agree though too use softer language in the vignettes ;]
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.
Don't mind if I do 😉