For the purpose of determining where custom defines and includes should
be added, the final location of the diagnostic is irrelevant: it's the
path to the compilation unit itself that matters, since that's where the
corresponding configuration is taken from.
If you have a missing include file in an include file, compilationUnit()
gives the path in which a custom include should be added, unlike
finalLocation().
| No Linters Available |
| No Unit Test Coverage |
Hey there,
since this wasn't merged, I assume you don't have commit rights. I will gladly commit this for you, but I need to know your name and email address. I'll put that into the git author field then, to keep this patch attributed to you
Thanks
Name & email address could be taken from the data in identity.kde.org (which also matches the one used at https://github.com/nhaehnle, thus seems okay as public info).
Hi @nicolaih, it would still be good to have you confirm here that using these data is also okay for this patch. TIA