-
Notifications
You must be signed in to change notification settings - Fork 12
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
Check .clangd configuration file syntax #247
Milestone
Comments
Can we create an error marker for the problematic clangd file? |
That's exactly what I'am currently working on :-) |
:-) Brilliant! |
ghentschke
added a commit
to ghentschke/eclipse-cdt-lsp
that referenced
this issue
Feb 6, 2024
- Inform the user via markers in the .clangd file when the syntax cannot be parsed, because this leads to problems in the ClangdConfigurationFileManager.
ghentschke
added a commit
to ghentschke/eclipse-cdt-lsp
that referenced
this issue
Feb 7, 2024
- Fetch info from MarkedYAMLException to create a marker for the .clangd file. fixes eclipse-cdt#247
ghentschke
added a commit
to ghentschke/eclipse-cdt-lsp
that referenced
this issue
Feb 7, 2024
- add unit tests
ghentschke
added a commit
to ghentschke/eclipse-cdt-lsp
that referenced
this issue
Feb 7, 2024
- fix review comments
ghentschke
added a commit
to ghentschke/eclipse-cdt-lsp
that referenced
this issue
Feb 8, 2024
- fix review comments - use IResource.DEPTH_ZERO in deleteMarkers, since the config file has no members.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because of #245, the user has to be informed, that the yaml syntax is invalid. It's assumed that the user has no yaml editor in his Eclipse IDE and if so, the
.clangd
file would not be recognized as yaml file since it has no file ending.The text was updated successfully, but these errors were encountered: