Feature Request: Allow additional xmllint parameters

[tkalmar]

For an xml with very large text nodes i got errors like:

Error: file_0.xml:17: parser error : xmlSAX2Characters: huge text node
file_0.xml:17: parser error : Extra content at the end of the document

This also happens with command line xmllint
When passing the --huge parameter the errors go away and linting works as expected.

Is it possible to support additional parameters to pass to xmllint?

My workaround at the moment is to pass an additional xml to the validation process
{ contents: '', fileName: '--huge' } as the filename gets pushed to the args array this works but is a little bit hacky

[noppa]

Sounds like a useful feature. Should be pretty easy to add to options and somewhere around

xmllint-wasm/src/index.js

Line 37 in 5cb5744

const args = [];

I can accept PRs, or might look at implementing this myself in a week or two.

[noppa]

I have just published vesion 5, and it has an option modifyArguments that lets you do this.

const result = await xmllint.validateXML({
  xml: myXml,
  schema: mySchema,
  modifyArguments(args) {
    return [...args, '--huge']
  }
});

I have also added validation against using the fileNames for custom arguments. I think it's possible that some people are taking file names from user input, so letting those control the behaviour of the lib feels like a footgun.