Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Adds a new MISRA C++:2023 query implementation and test coverage for RULE-10-1-2 (“The volatile qualifier shall be used appropriately”), and wires it into the rule/package infrastructure.
Changes:
- Register RULE-10-1-2 in
rules.csvunder the newDeclarations4package. - Add rule package metadata for
Declarations4and a new query implementation for RULE-10-1-2. - Add a dedicated unit test directory with
.qlref,.expected, andtest.cppcases.
Reviewed changes
Copilot reviewed 8 out of 8 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| rules.csv | Points RULE-10-1-2 at the new Declarations4 package and fills in the mapping field. |
| rule_packages/cpp/Declarations4.json | Introduces package metadata for RULE-10-1-2 query. |
| cpp/misra/src/rules/RULE-10-1-2/VolatileQualifierNotUsedAppropriately.ql | New CodeQL query implementing RULE-10-1-2. |
| cpp/misra/test/rules/RULE-10-1-2/test.cpp | Adds COMPLIANT/NON_COMPLIANT test cases for the new query. |
| cpp/misra/test/rules/RULE-10-1-2/VolatileQualifierNotUsedAppropriately.qlref | Hooks the test directory to the production query. |
| cpp/misra/test/rules/RULE-10-1-2/VolatileQualifierNotUsedAppropriately.expected | Expected results matching the NON_COMPLIANT annotations. |
| cpp/common/src/codingstandards/cpp/exclusions/cpp/Declarations4.qll | Adds autogenerated exclusions metadata wrapper for the new query. |
| cpp/common/src/codingstandards/cpp/exclusions/cpp/RuleMetadata.qll | Updates query metadata wiring, but currently contains an unresolved merge conflict. |
cpp/common/src/codingstandards/cpp/exclusions/cpp/RuleMetadata.qll
Outdated
Show resolved
Hide resolved
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
please enter the description of your change here
Change request type
.ql,.qll,.qlsor unit tests)Rules with added or modified queries
Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:
If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?
🚨🚨🚨
Reviewer: Confirm that format of shared queries (not the .qll file, the
.ql file that imports it) is valid by running them within VS Code.
Reviewer: Confirm that either a change note is not required or the change note is required and has been added.
Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
Reviewer
As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.