@shati-patel, could you take a look at the query help? Here is a preview.

@shati-patel, could you take a look at the query help? Here is a preview.

Thanks, the documentation mostly looks clear! I've made a few suggestions based on our existing style guide. (I can't comment on the .qhelp inline, so here they are:)

• "For example, when using the github.com/ChrisTrenkamp/goxpath API, you can do this by creating a function that takes an *goxpath.Opts structure."
• "This function can then be specified when calling Exec(), Exec{Bool|Num|Node}(), ParseExec(), or MustExec()."
  (comma after ParseExec())
• "In the first example, the code accepts a username ..."
• The code in the example overflows outside the box:
  
  This may just be a problem with the preview, but if you're able to make the lines shorter that might be a good idea.

Thanks again! This is getting there, but I think I'd like to see a few more tests for the various cases.

How many tests do you want?
Also, stubbing is quite tedious, is there an easy way to create stubs instead of creating them by hand?

Many thanks for you continued efforts!

Ideally we'd like one test per supported library.

stubbing is quite tedious

Unfortunately, yes. I don't know of a way to automate it.

The query doesn't find any results on LGTM.com at the moment, which isn't entirely unexpected.

I've added a change note and a precision modifier.
Since most Xpath injection queries in other languages are @precision high I've defaulted to this value here as well.

Thanks! @precision high should be fine, seeing as my run across all of LGTM.com above didn't find any results.

Once @sauyon has done the evaluation, this is good to go in.

🎉 Thank you for your contribution, @intrigus-lgtm.

Thank you for guiding me and answering all my questions :)