Qodana Community for JVM

It seems all right 👌

No new problems were found according to the checks applied

💡 Qodana analysis was run in the pull request mode: only the changed files were checked

      - name: 'Qodana Scan'
        uses: JetBrains/qodana-action@v2025.2.1
        with:
          upload-result: true

@xepozz Does this look fine?

Thanks @xHeaven. I've tried to perform such collecting, but nothing worked.
The way is simple:

• Target to a File in Injector
• Find XmlValue/etc manually with PsiTreeUtil
• Inject as it is now

But PHP layer don't work in this way, all completion is broken.

I've pushed a minor refactoring, I'm ok to merge it.

The picture I attached to the previous post is related to the web types. Lets disable injections from the web types / symbols, they block our manual injection. Can you check?

Interesting, which one do you think holds more value as it is right now, web types or autocomplete?

With web types, we have less autocomplete, but the IDE is less of a Christmas tree.
Without web types, we get autocomplete along with all kinds of issues such as syntax errors and attribute warnings:

We also have a weird issue where we type the variable called $item wrongfully for no apparent reason - not introduced in this PR but weird regardless:

I'm not sure we should disable web types just to make the feature in OP work, more like we should fix the behavior of web types, but that's out of the scope of this PR.

We could probably do either:

• wait with merging this PR, find a solution for the web types issue and merge later
• merge regardless (autocomplete still works outside of Tempest built-in attributes), and find a solution for the web types issue later

What are your thoughts?