Skip to content

Project selection should incorporate whether or not a project is "valid" #1408

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

Open
thecrypticace opened this issue Jun 9, 2025 · 0 comments
Assignees

Comments

@thecrypticace
Copy link
Contributor

See #1406 (comment)

The idea here is that during project matching, if possible, we should check to see if the project is valid and skip projects that are not. Now this is a bit complicated because projects are initialized lazily but I think we can change project selection behavior if a project is initialized and detected to have an invalid config or CSS or something.

Additionally, we should capture and surface errors parsing CSS files for v4 so they can be displayed right in the editor. The errors don't surface source location information currently so they should be pinned to 0:0 in the CSS file. Once we start throwing errors with source location information IntelliSense can more intelligently place the errors.

@thecrypticace thecrypticace self-assigned this Jun 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant