Added docstrings to exported functions!#547
Conversation
|
@ValentinKaisermayer and @iblislin |
ValentinKaisermayer
left a comment
There was a problem hiding this comment.
LGTM, just two minor comments.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #547 +/- ##
==========================================
+ Coverage 85.44% 85.45% +0.01%
==========================================
Files 11 13 +2
Lines 625 887 +262
==========================================
+ Hits 534 758 +224
- Misses 91 129 +38 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
|
@ValentinKaisermayer It's done kindly review it and if there are any more changes to notice and fix then please do let me know! |
|
maybe some of the docstring could be shared in the |
|
Thanks for your contributions. |
|
Thank you @iblislin |
|
Shouldn't Documenter.jl put them there automatically? |
well, no. since there aren't any docstrings before, they aren't included in doc/. |
Maybe we should add an API section like this # API Documentation
```@autodocs
Modules = [TimeSeries] |
This PR addresses issue #533 by ensuring that all exported methods in TimeSeries.jl have comprehensive docstrings.
The following actions were taken:
Reviewed all exported functions, types, and constants.
Added or improved docstrings for any missing or incomplete documentation.
Followed the existing documentation style for consistency.
Included examples where helpful.
Motivation:
Having complete docstrings for all exported methods improves usability and discoverability for users, making the package easier to use and understand.
Notes:
All existing tests are passing. No change was done to code just documentation-only fixes were done.
Reviewers:
@ValentinKaisermayer @iblislin