-
Notifications
You must be signed in to change notification settings - Fork 4
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
docs: Improve wording on stating that a method does not work in-place #346
Labels
cleanup 🧹
Refactorings and other tasks that improve the code
documentation 📖
Improvements or additions to documentation
released
Included in a release
Comments
This part of the issue will be resolved by #427. |
Blocked by #58 (which will add a bunch of new methods / docstrings in the |
zzril
added a commit
that referenced
this issue
Jul 13, 2023
…#449) Closes #346 ### Summary of Changes Updated the docstrings of methods in `src/safeds/data` to state that copies are returned, with the original object left unmodified. --------- Co-authored-by: Alexander <[email protected]> Co-authored-by: megalinter-bot <[email protected]>
🎉 This issue has been resolved in version 0.15.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
cleanup 🧹
Refactorings and other tasks that improve the code
documentation 📖
Improvements or additions to documentation
released
Included in a release
Describe the bug
For methods that return a copy, rather than working in-place, I believe the standard wording in docstrings is:
Currently, we have this sentence in most of our docstrings:
Might be unclear for some users what "this table" refers to.
This rule should also be added to the guidelines.
Certainly wrong is this:
Expected behavior
Agree on a standard wording to use everywhere.
Definitely fix the redundancy in
tag_columns
insrc/safeds/data/tabular/containers/_table.py
.The text was updated successfully, but these errors were encountered: