After fixing errors validator still shows error about exalt

[eerohele]

I can't immediately reproduce the issue.

Are you able to share the XML document you're using, or a snippet from it?

[eerohele]

Hmm, in fact, it looks like it occurs when editing an XML document without a DTD or other schema declaration.

Thanks for reporting, I'll look into it.

[eerohele]

All right, I have a fix that I think should work, but I'll need to run some tests first. I'll try to cut a new release pretty soon.

[eerohele]

I've released v0.3.4, which should fix this issue. It'll take a while to appear on Package Control, but it should be there tomorrow at the latest.

If you can, can you please confirm that the issue is resolved? If not, I'll reopen the issue.

[infotexture]

👍 v0.3.4 from Package Control seems to resolve the issue.

I was able to reproduce the issue before upgrading, but with 0.3.4 the error disappears as soon as the invalid XML is corrected.

[SASkievua]

yes, 0.3.4 fixed the issue!
thank you for quick fix!
and for the great plugin you done!

[eerohele]

Glad to hear it, and thanks to you both for checking back!

[ArturoRR97]

Im using v0.3.4 and when I modify and save the schema, to validate the xml with the new changes on the schema I need to restart sublime text . Once I close and reopen sublime text the validetor works fine.

[eerohele]

@ArturoRR97: Does this comment help with that issue?

[ArturoRR97]

Thanks for the fast replay, but what I meant was that the problem remains. It is not enough to close and open the files, instead is necessary to close and open sublime text each time you make changes to your schema.
This are the files I am using, when I change the restriction I need to close sublime to properly validate the xml with the new restriction.

[eerohele]

What I meant was, running the "Exalt: Clear Parser Cache" command via the Sublime Text command palette should make the schema changes take effect without you having to restart Sublime Text. Did you try that?

[ArturoRR97]

Many thanks that solve my problem. Sorry for the annoyance.

[eerohele]

No annoyance — that information really should be in the README.