Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Re-adjusted error range for bad schema location, need to filter it out duplicates #361

Merged
merged 1 commit into from
May 6, 2019
Merged

Re-adjusted error range for bad schema location, need to filter it out duplicates #361

merged 1 commit into from
May 6, 2019

Conversation

NikolasKomonen
Copy link
Contributor

@NikolasKomonen NikolasKomonen commented Apr 26, 2019 •
edited
Loading

Fixes #336, #343

@NikolasKomonen NikolasKomonen force-pushed the schemaReferenceError branch 2 times, most recently from 5aa582d to 2226771 Compare April 26, 2019 16:55
@NikolasKomonen
Re-adjusted error range for bad schema location, need to filter it ou…
681fc64 
…t duplicates

Fixes eclipse-lemminx#336, eclipse-lemminx#343

Signed-off-by: Nikolas Komonen <nikolaskomonen@gmail.com>
@NikolasKomonen NikolasKomonen force-pushed the schemaReferenceError branch from 2226771 to 681fc64 Compare May 6, 2019 20:01
@NikolasKomonen
Copy link
Contributor Author

@fbricon updated

@fbricon fbricon merged commit d3a3d61 into eclipse-lemminx:master May 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fbricon fbricon fbricon requested changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Missing schema generates too many warnings
2 participants
@NikolasKomonen @fbricon