Missing dependency substitutions

[bpappin]

When importing live projects with dependency substitution, the the substituted projects are not visible and editable.

The point of doing this is so that you can manage the code in both at the same time.
The projects should show up under separate entries at the root, so they are easily distinguishable.

I usually use the Project Files view, because it shows them and shows the correct KMP folders.

Example import substitution:

includeBuild("../my-project-dir") {
    dependencySubstitution {
        substitute(module("com.example.core.thingy:core-thingy")).using(project(":core-thingy"))
    }
}

[bpappin]

FYI - I love that this plugin exists, its long overdue.

[Bhuvaneshw]

Can you provide visual representation of how it is showing currently and how should it show in project view?

[bpappin]

Can you provide visual representation of how it is showing currently and how should it show in project view?

I think you can choose to make it better if you can come up with a way, but right now it shows as a list of projects with substitutions. The main project is the one labeled "Missions".

Personally, I like them laid out this way, as a list of projects, because I can dig into any one of them at the same time (which is what this particular substitution is for).

I would say that you should set up a project like this, and see what you like best.

[Bhuvaneshw]

Ok, I'll try!