Replies: 1 comment
-
Hi @BenJoice 👋🏻 Sorry to hear that you're having problems with your own packs and queries. Our documentation should generally be up-to-date, but if you are coming across documentation that isn't right, let us know and we can fix it.
I am not sure what you mean by "Corel". If you mean CodeQL, then you can follow e.g. the documentation at https://docs.github.com/en/code-security/codeql-cli/using-the-advanced-functionality-of-the-codeql-cli/using-custom-queries-with-the-codeql-cli and subsequent pages.
I am not sure which "http method" you are referring to. Could you be more specific?
Generally, we try to make backwards-compatible changes. Occasionally, we will deprecate parts of the libraries and mark them as such, but they continue to function for some time until they are removed. If you are having difficulty migrating a particular query you wrote, feel free to share details about the problems you are running into and we can help you get them fixed.
It's not necessary to create a different qlpack for each rule. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Is there a correct way to write rules for Corel and integrate them into the Cli?
I encounter problems supporting both old rules and new ones, for example, the http method in the new version is deprecated, respectively, if you use the new qlpack (whose syntax has also changed), the rule will break. How do I update the codeql version and rules correctly?
Where can I get information about current methods? Is there any agreement on which qlpack format is the norm now and whether it is necessary to create a different qlpack for each rule?
I will be glad of your help.
Beta Was this translation helpful? Give feedback.
All reactions