-
Notifications
You must be signed in to change notification settings - Fork 93
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
Changing the file associations or catalogs in the preferences should trigger validation #143
Comments
Changing content of XML Schema/DTD should trigger too validation. We could start to trigger validation for all opened XML document and after we could improve it to validate only XML document which is linked to the XML Schema/DTD which changed. |
It should work. We need to write tests. |
It should work now, please give me feedback. |
I confirm this works. Do we have regression tests for that? |
No taht's why I have not closed it |
Closes eclipse-lemminx#143 Signed-off-by: Nikolas <[email protected]>
Closes eclipse-lemminx#143 Signed-off-by: Nikolas <[email protected]>
Closes eclipse-lemminx#143 Signed-off-by: Nikolas <[email protected]>
Closes eclipse-lemminx#143 Signed-off-by: Nikolas <[email protected]>
Closes eclipse-lemminx#143 Signed-off-by: Nikolas <[email protected]>
Closes #143 Signed-off-by: Nikolas <[email protected]>
When a file association or a catalog is added or modified in the preferences, if a matching document is already open, it doesn't take into account the new schema.
Either diagnostics on opened documents are stale or missing.
So changing associations or catalogs should trigger validation for all opened documents.
The text was updated successfully, but these errors were encountered: