monorepo with different abl projects

[jmls]

Is it possible to configure the plugin to handle multiple ABL projects within a monorepo ?

Each project would have it's own propath, db connections etc

I'm not sure that profiles fit the bill, as it seems to be orientated for different abl versions. Or can they be "manipulated" to support a monorepo ?

[kenherring-rkt]

This would be very helpful for us as well. Ideally having configuration similar to the sonar "submodules" work would be fantastic.

[gquerret]

Assuming your monorepo structure is like that:

root
 \_ oe_project1
     \_ openedge-project.json
 \_ oe_project2
     \_ openedge-project.json
 \_ node_project1
 \_ ...

You can have a .code-workspace file in the root directory, which contains references to oe_project1 and oe_project2. The language server will then try to open the configuration file of each project of the workspace.

[PeterJudgeZA]

FWIW this is an approach we take.

[gquerret]

@jmls @kenherring-rkt Did you try opening vscode with the workspace configuration ?

[kenherring-rkt]

Didn't love how it worked for us - mostly because we have files for different "projects" comingled in directories. Probably not worth fixing and just something we have to deal with.