feat(better-code-generation) #99
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…pth prompt guidelines
Owner
|
Hey @Ranieri93 it looks great! Thanks for the contribution and sorry for the late review. I'll release a new version soon |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR aims to tackle #79
It introduces a pre-execution linting step to automatically fix and validate LLM-generated code, and integrates a comprehensive set of Node.js best-practice guidelines into the main prompt to guide the model toward better output.
What's New?
** Enhanced Node.js Guidelines (NODE_GUIDELINES.md) **
A detailed set of guidelines for writing modern, secure, and performant Node.js code has been created.
These guidelines are now automatically injected into the run-node-js-script prompt in server.ts, providing the LLM with clear instructions on best practices (e.g., use ESM, async/await, fetch, and secure coding patterns).
** On-the-fly Code Linter (src/linterUtils.ts) **
Before execution, all user-submitted code is now passed through a new ESLint-based linter.
The linter automatically fixes common stylistic and syntax errors (e.g., converting var to const, fixing spacing)
If unfixable errors are found (like using an undefined variable), a clear report is returned to the user, making debugging much easier.