-
Notifications
You must be signed in to change notification settings - Fork 80
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
ai-based doc cleanup #155
ai-based doc cleanup #155
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @iboates, Thanks for this PR. Overall it looks good. I suggest to somehow include the notes part in the code. If the note section is raising some issue, I suggest to move it up, in the starting section of the docstring.
Apart from that, it looks good to me.
|
||
Notes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
is it possible to preserve these notes?
|
||
Notes | ||
----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notes
|
||
Notes | ||
----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Notes
|
||
Notes | ||
----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
|
||
Notes | ||
----- | ||
The name of the style file will be, rasterName:workspace |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
|
||
Notes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
|
||
Notes |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
|
||
|
||
Notes | ||
----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
|
||
Notes | ||
----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
notes
Sure, I also noticed that some of the nice organizational headers were removed by the almighty wise and all-knowing AI, I will put them back as well |
@iamtekson Restored the notes and other comments |
@iamtekson Do you have any more input? Or can I merge? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for taking so long. Yes, it looks good to me! We can merge it now.
Closes #46
This PR is actually very AI-heavy. I used ChatGPT to tidy up the existing docstrings and create ones where they were missing. I validated them afterwards and I found no problems. Despite this, I put a disclaimer on the API docs page because I believe that AI-generated contributions and content should always be disclosed.
Incidentally, the api docs page is currently broken. I built the docs locally and they seem to work now: