We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Text content provider not called in positions right before opening tag and immediately following closing tag.
The following tests help to identify the problem.
it("in position immediately following a closing tag", () => { const sample = `<person address="NY">\n` + `\t<firstname>Anna</firstname>⇶\n` + `\t<lastname>Smith</lastname>\n` + `</person>`; let providerCalled = false; getSampleSuggestions(sample, { attributeName: [ ({ element, attribute, prefix }) => { expect(element.name).to.eql("person"); expect(attribute).to.be.undefined; expect(prefix).to.be.undefined; providerCalled = true; } ] }); expect(providerCalled).to.be.true; }); it("in position right before an opening tag", () => { const sample = `<person address="NY">\n` + `\t<firstname>Anna</firstname>\n` + `\t⇶<lastname>Smith</lastname>\n` + `</person>`; let providerCalled = false; getSampleSuggestions(sample, { attributeName: [ ({ element, attribute, prefix }) => { expect(element.name).to.eql("person"); expect(attribute).to.be.undefined; expect(prefix).to.be.undefined; providerCalled = true; } ] }); expect(providerCalled).to.be.true; });
The text was updated successfully, but these errors were encountered:
Thanks for providing the example tests, it is probably some offset by 1 logic error 😄
Sorry, something went wrong.
bd82
No branches or pull requests
Text content provider not called in positions right before opening tag and immediately following closing tag.
The following tests help to identify the problem.
The text was updated successfully, but these errors were encountered: