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

Ensure code quality / formatting on write #112

Open
lily-de opened this issue Oct 4, 2024 · 1 comment
Open

Ensure code quality / formatting on write #112

lily-de opened this issue Oct 4, 2024 · 1 comment
Labels
enhancement New feature or request hacktoberfest Good ticket to tackle as part of Hacktoberfest help wanted Extra attention is needed

Comments

@lily-de
Copy link
Collaborator

lily-de commented Oct 4, 2024

We have noticed Goose having issues with whitespacing/formatting with Python, and also producing errors with JS. It seems like this rarely happens the first time you ask it to do something, but if you ask it to repeatedly edit a file, it seems like it inevitably runs into issues. Not sure if anyone else has run into this. Could be an issue with how it sends data to be reprocessed after an initial request (just spitballing).

Potential approach: pair it with a linter/formatter (like black) and prompt with something like "the task is not successful until it passes this linter"

@lily-de lily-de added enhancement New feature or request help wanted Extra attention is needed hacktoberfest Good ticket to tackle as part of Hacktoberfest labels Oct 4, 2024
@handstandsam
Copy link

It's possible to give goose acceptance commands in a plan. One of those can be successful formats. That should work 😄 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest Good ticket to tackle as part of Hacktoberfest help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants