-
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
Follow docstring conventions #106
Comments
hi! Thanks for bearing with us on this :-) we are still learning a lot |
Hm, I installed this branch, but the docstring doesn't look any different, not sure if I did it correctly?
I also wanted to add that my comment about default arguments applies to other functions/objects as well, e.g. |
No idea either. I simply installed it with
This should be correct? |
Did you restart the REPL? Sometimes I have noticed it doesnt update the package - I just tried with can you doublecheck with |
Ah yes, restarting the REPL fixed it! Thanks! The comment on following established standards (specifically with respect to arguments) still stands though. |
predef_eeg
seems to be broken
This issue is part of openjournals/joss-reviews#6641.
As @roualdes has already mentioned in #95, the docstring for
predef_eeg
seems to be broken. Since this is likely one of the first functions that new users will interact with, I think it is really important to get this docstring right. I'm not sure what's going on, but it seems like underscores are mangled with the following characters and interpreted as an underline.In addition, I strongly suggest to follow Julia standard docstring conventions. Currently, the structure differs quite a lot from what I'd expect. For example, I find it quite difficult to get to know the signature when the various kwargs are not listed in a single place. This is especially important because usually I'd like to see all the default values just to know which arguments are required.
If you compare this to the doc of e.g.
LinearAlgebra.svd
, I'd recommend to implement something that follows what they are doing (which seems to be the standard):The text was updated successfully, but these errors were encountered: