Intellij Idea workspace module support

[rauanmayemir]

I couldn’t make the plugin work when my code is added as a PHP module in an IDEA project )(workspace).

Couldn’t even update the settings of mago, looks like the plugin needs to account for workspaces.

[xepozz]

hey @rauanmayemir !
sorry, missed the issue

do you have an available demo project with the problem?

[rauanmayemir]

@xepozz I've only tried from within my monorepo, but it is as easy as creating a new module in an empty project:

Then Mago settings become as if non-responsive, so changing executable path doesn't activate 'Apply' button:

[rauanmayemir]

I'm currently on IntelliJ IDEA 2025.2.3

[xepozz]

@rauanmayemir

I've made an early build. Could you please test?

Mago-2025.0.5.zip

[rauanmayemir]

@xepozz Thanks, this works. However, I'm not sure it's actually analyzing anything.

[xepozz]

Seems like your source code is outside of mago scope. That's why I asked about the project demo.
Could you please describe how your project looks like?

[rauanmayemir]

Yeah, the code is inside a module. Modules have a so-called content root. I think mago scope needs to be applied to the module, not workspace. https://www.jetbrains.com/help/idea/creating-and-managing-modules.html

| project_dir (aka workspace)
| –– myphpapp

[xepozz]

Do you have in mind tools that works with the modules well?

[jskorlol]

It seems this doesn’t work in my case either.

When your project structure looks like this:

project/
├─ backend/
│  └─ vendor/bin/mago
├─ frontend/
└─ README.md

and the Laravel application is located one level deeper inside the project, Mago doesn’t appear to pick it up correctly.

It looks like Mago does not automatically detect the Laravel root when it is nested under another directory. Because of that, the formatter and linter configuration are not applied unless Mago is executed from the backend directory directly.

Is there any way to make Mago automatically recognize and handle this kind of nested Laravel project structure?

For comparison, the Laravel Idea plugin allows explicitly configuring the Laravel root directory, which makes this setup work without issues.

Is a similar configuration option or auto-detection mechanism planned or supported in Mago?

[xepozz]

2025.1.2 version works as regular php tool: laravel pint, csfixer, etc
@jskorlol Could you please try again with the newest build?

[jskorlol]

@xepozz It’s resolved now. Thank you! I’ll give Mago a try.

[jskorlol]

Ah, never mind. It’s working, but the problem is that even though the backend/mago.toml file exists, it doesn’t seem to be reading it. The custom formatting I applied isn’t being applied.

[xepozz]

Ah, never mind. It’s working, but the problem is that even though the backend/mago.toml file exists, it doesn’t seem to be reading it. The custom formatting I applied isn’t being applied.

Formatter doesn't use the config file. I'll add it too