-
Notifications
You must be signed in to change notification settings - Fork 45
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
Invalid suggestion created #32
Comments
That's a very odd suggestion! My suspicion is that it's due to that header file requiring Qt's moc. I'm not sure how you should best handle that -- maybe either run moc over the headers first? Or just exclude them from clang-tidy-review? |
moc runs over pretty much the entire codebase as far as I know, I don't think there is much I can do about it. |
I thought it only applied to the headers? At any rate, I'm afraid I think this is an issue between clang-tidy and Qt -- you would have the same issue running clang-tidy locally. I think you'll need to either generate the "real" C++ headers first, or tell clang-tidy to ignore all the header files. |
|
Ah, ok! Interesting that those are also different warnings from clang-tidy-review Could you re-run it with |
I think the warnings were different because I ran just one check only - re-running it again with export-fixes and the same checks string, here is the resulting file. |
It looks like maybe I think it might be a good idea for |
That would be a good debugging opt-in feature! |
Hi @ZedThree most likely the reason for such an invalid suggestions is this: |
Ah, amazing, thanks @oleg-derevenetz! It looks like it needs a combo of checking out a different ref and then also getting the PR base as well. Hopefully we could at least automate that second part |
Check out Mudlet/Mudlet#5981 (comment) - the action generated a syntactically invalid C++ suggestion by the looks of it?
The text was updated successfully, but these errors were encountered: