-
Notifications
You must be signed in to change notification settings - Fork 22
[LSP] tell the client why the codeflash config is not valid #806
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
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
| if "tests_root" not in config or config["tests_root"] is None or not Path(config["tests_root"]).is_dir(): | ||
| return None | ||
| if not Path(tests_root).is_dir(): | ||
| return None, f"Invalid 'tests_root': directory does not exist at {tests_root}" |
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.
nit: We can do test framework check later in this.
PR Type
Enhancement, Bug fix
Description
Return specific config validation errors to clients
Improve pyproject.toml validator with detailed checks
Adjust LSP responses to include failure reasons
Minor variable rename to avoid unused warning
Diagram Walkthrough
File Walkthrough
cmd_init.py
Enrich pyproject.toml validation with reasonscodeflash/cli_cmds/cmd_init.py
beta.py
Include validation reason in LSP error responsecodeflash/lsp/beta.py