Skip to content
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

Update / generate the docstrings #994

Merged
merged 27 commits into from
Feb 13, 2024

Conversation

kristiankyvik
Copy link
Collaborator

@kristiankyvik kristiankyvik commented Jan 31, 2024

This PR generated the docstrings in the NumPy style for all the code. In some cases it also updates outdated docstrings.

As suggested by @ATheorell, I used gpt-engineer CLI to generate all of docstrings.

This will properly populate the API reference section of the gpte-engineer docs (see image below):

CleanShot 2024-01-31 at 17 07 14@2x

I think we should try to merge this PR before, that fixes the documentation build before merging this one as described in the original issue.

@kristiankyvik kristiankyvik marked this pull request as draft February 2, 2024 12:53
@kristiankyvik kristiankyvik marked this pull request as ready for review February 6, 2024 10:38
@@ -221,10 +316,22 @@ def get_files_from_toml(self, input_path, toml_file):
return selected_files

def merge_file_lists(
self, existing_files: list[str], new_files: list[str]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Out of curiosity, did you do this @kristiankyvik , or was this an automatic type correction?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was GPT-engineer. Despite me explicitly requesting it to limit itself to adding/editing docstrings, in some cases, it took the liberty of also correcting the parameter types. I figured I would also keep these suggestions in the PR after manually reviewing them.

@ATheorell
Copy link
Collaborator

Wow, massive PR! Great work. Its so comprehensive I didn't read it all. Is there any reason why we should not merge it @kristiankyvik , if not, I'll click the button :)

@kristiankyvik
Copy link
Collaborator Author

I see no reason for us not to merge this other than us perhaps merging this PR first as this should fix the docs build. I already made some changes to the PR based on your feedback from yesterday.

@kristiankyvik
Copy link
Collaborator Author

I think this can be merged now, @ATheorell since #999 has been merged.

We are now down to only 18 errors, all related to static files that will be addresses in the last PR of this series, #996.

@ATheorell ATheorell merged commit 19446fa into gpt-engineer-org:main Feb 13, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants