document

[timelyportfolio]

I believe the API is stable enough to begin documenting in roxygen and also in other supplementary materials, such as vignettes and articles.

[JasonCurole]

@timelyportfolio are you still looking for support on this?

[timelyportfolio]

@JasonCurole yes definitely - documentation is the only obstacle between current state and CRAN. Happy to discuss.

[JasonCurole]

Great. Happy to help. I'm new to contributing, but I've been using dataui (both on its own and through reactablefmtr) and am very appreciative. Let me know the best way for us to discuss.

[timelyportfolio]

@JasonCurole thanks so much again for potentially helping. I forgot that I started documentation very similar to what I envision for the remaining componentss in dui_histogram and dui_sparkline. Would this be sufficient to establish a pattern that we might be able to use as a model for the components in components.R? Most of the arguments are in storybook | props table tab and/or in github repo readme. I remember not all of these are exactly correct or maybe even available, but I did not list these back when I was working on building the package.

Also, I think instead of ... as the arguments for components, an R user might benefit from named arguments similar to dui_sparkline arguments.

I started with dui_sparkbarseries in this commit as an example.

If you still have interest, document away :). Let me know how I can help.