-
Notifications
You must be signed in to change notification settings - Fork 1.8k
QL handbook: Update process for module resolution #3714
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.
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
Conversation
@hmakholm, this description is deliberately not too detailed, but could you verify it's still correct? |
lgtm |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fair. My comments are just quibbling and can be ignored if you want.
contain ``<queries language="javascript"/>``.) | ||
#. If that fails, it looks up ``examples/security/MyLibrary.qll`` relative to the query | ||
directory, if any. | ||
The query directory is the first enclosing directory containing a file called ``qlpack.yml``. (Or, in legacy products, a file called ``queries.xml``.) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"First" is a bit ambiguous here -- but I'm not sure how to say it better without sounding excessively technical.
#. If no file is found using the above two checks, it looks up ``examples/security/MyLibrary.qll`` | ||
relative to each library path entry. The library path depends on the environment where you | ||
#. If the compiler can't find the library file using the above two checks, it looks up ``examples/security/MyLibrary.qll`` | ||
relative to each library path entry. The library path depends on the tools you use to |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Even in an abbreviated description, I think it would be helpful to reveal that this is where the libraryPathDependencies
of qlpack.yml
comes in. We could still omit the details of how exactly it comes in -- just words that amount to "trouble locating imports? check your libraryPathDependencies".
Thanks @hmakholm - good point about the |
Co-authored-by: Henning Makholm <hmakholm@github.com>
Thanks 😄 |
Uses the detailed description from the QL spec (#3476) to update the more lightweight description of module resolution in the QL handbook.