-
-
Notifications
You must be signed in to change notification settings - Fork 14
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
Pre-release activities - vignettes review #640
Comments
The example apps in the vignettes are quite verbose, e.g. very long example
What do you think about assigning modules as separate variables to make the
|
Yes, this makes a huge sense! +1 |
Another thought: do you think it would be beneficial to add |
I think |
When running the example app from the vignette Cannot merge at least two dataset extracts. Make sure all datasets used for merging have appropriate keys. |
Definitely data-extract/data-merge problem. We have something to debug here |
Changing the |
🤦🏽 The created |
Closes #640 --------- Signed-off-by: Vedha Viyash <[email protected]>
I think we can remove |
I agree, I don't see much value in having |
PR to #640 --------- Signed-off-by: Vedha Viyash <[email protected]> Co-authored-by: kartikeya <[email protected]> Co-authored-by: Vedha Viyash <[email protected]>
Hey @kartikeyakirar did you mind looking at this comment |
@m7pr I assigned modules to separate variables for a more concise |
Well, that's up for discussion. I think vignettes definitely benefit from this, so there at least. I myself run example apps for modules in the browser as well (but I don't want to set it as IDE default because I still want small apps to launch in the RStudio panel) so it would work for me but not necessarily for others. |
I added a separate task for discussion. This needs to be applied to all package vignettes for consistency. insightsengineering/nestdevs-tasks#53 |
Part of #624 related to vignettes. Please make a PR to pre-
release@main
The text was updated successfully, but these errors were encountered: