-
Notifications
You must be signed in to change notification settings - Fork 1.5k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
fixed #12763 - do not assert in markup processing for `unusedFunction…
…` when a language is enforced (#6425)
- Loading branch information
Showing
4 changed files
with
31 additions
and
4 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
9c21862
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.
I wonder if we shouldn't have a "markup" enum constant anyway. if we have a markup enum constant then we can skip certain steps for markup files for instance symboldatabase , valueflow , etc. or do you skip those steps in some other way? We also don't want to run the usual checkers on qml files as far as I know.
Spontanously it feels a bit weird to change the language for a markup file. I can see why --language will determine the language for a markup file. But at the same time.. a qml file does not have C or C++ code.. and if the user provides configuration that says qml is a markup extension then maybe we can respect that.