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

[Feature]: Enable Automatic Linting After File Edits #6265

Open
openhands-agent opened this issue Jan 14, 2025 · 0 comments
Open

[Feature]: Enable Automatic Linting After File Edits #6265

openhands-agent opened this issue Jan 14, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@openhands-agent
Copy link
Contributor

What problem or use case are you trying to solve?
The goal is to implement an automated linting feature that executes whenever a file edit is made. This aims to catch errors earlier in the development process to improve accuracy and efficiency.

Describe the UX of the solution the user wants
Automatically run a linter script, such as openhands_lint.sh, after every file edit if the script exists.

User's thoughts on the technical implementation?
The approach could leverage existing configurations used by developers, such as the pre-commit-config.yml, to ensure consistency between human and automated edits.

Describe the alternatives considered
Catch errors at the commit stage was considered, but executing the linting post-edit is more advantageous to catch errors sooner.

Additional context
This feature will align with existing practices, like the swe-agent using flake8 for Python files, which currently rejects edits not passing lint checks.

Issue Created By: Graham Neubig on Slack

Link to Slack Thread: Slack Thread

@mamoodi mamoodi added the enhancement New feature or request label Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants