-
-
Notifications
You must be signed in to change notification settings - Fork 771
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
Doc: type and symbol solving #2259
Comments
Is this the same as #1943 ? |
@BraisGabin yes thanks, this issue further improves the documentation. I closed the old one, since work is ongoing here in this issue. |
For anyone using Groovy and not Kotlin for Gradle, here is an example similar to the original posted by @schalkms:
In regards to "some peculiarities": maybe the entire output of 'unresolved references', 'cannot access' internal classes, and multi platform projects being experimental is among them? But, ignoring that, my rule relying on type solving now seems to work. At least, in simple projects. In a multi-project build of mine types of other projects cannot be loaded. It only works for type resolution within a single project. I tried adding
|
@Whathecode thanks for posting more helpful content. This will be added to the page as well. |
I just saw that the specific configured Instead, to get multi-project analysis, you need to pass all source folders of the projects you want to analyze to
|
How is the status of this issue? We did some improvements already in our documentation in this regard. Should we update the tasks that should be done so we can close this issue? |
I have a draft for this page. I'd love to pick it up and send it out for review in the next days (unless someone else wants to pick it up). |
Sure, go for it! |
Sorry for the inconvenience. This one is on me. |
* Add documentation page on type resolution Fixes #2259 * Update docs/pages/gettingstarted/type-resolution.md Co-authored-by: Brais Gabín <braisgabin@gmail.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Add note on lintWithContext Co-authored-by: Brais Gabín <braisgabin@gmail.com> Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com>
The page is now available here: https://detekt.github.io/detekt/type-resolution.html Feel free to contribute, open issues & give suggestions 👌 |
Great work! I will highlight it in the release notes to get further feedback. |
* Add documentation page on type resolution Fixes #2259 * Update docs/pages/gettingstarted/type-resolution.md Co-authored-by: Brais Gabín <braisgabin@gmail.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Add note on lintWithContext Co-authored-by: Brais Gabín <braisgabin@gmail.com> Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com>
* Add documentation page on type resolution Fixes #2259 * Update docs/pages/gettingstarted/type-resolution.md Co-authored-by: Brais Gabín <braisgabin@gmail.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com> * Add note on lintWithContext Co-authored-by: Brais Gabín <braisgabin@gmail.com> Co-authored-by: M Schalk <30376729+schalkms@users.noreply.github.com>
can we use this approach to run type resolutions? (detektMain?) |
On the homepage there should be a separate chapter regarding rules that use type and symbol solving and how to configure them in Gradle. The existing section are missing some essential information.
detekt main
-> see potential-bugs Deprecation does not work #2038 (comment)From the Slack chat:
The text was updated successfully, but these errors were encountered: