How to have multiple Plasmic projects in the same repo with conflicting component names?

Developer Support
1

We try to have multiple plasmic projects in the same repo. For that we need multiple plasmic.json files. We tried to just rename the existing plasmic.json file and this fails already with quite a strange error message:

$ plasmic sync
... works
$ mv plasmic.json plasmic-website.json
$ plasmic sync --config plasmic-website.json

Plasmic error: "srcDir" in plasmic.json is outside of .
2

You don’t need to use multiple plasmic.json; multiple projects can share the same plasmic.json. Just specify the projects you want to sync as plasmic sync -p P1 -p P2

3

The thing is we have name conflicts in the components of the two projects. Thus we thought we could just generate the code completely independent to avoid them.

4

Or is there a better way to handle name conflicts in different projects?

5

hmm could you try passing a full path to --config?

6

This works: plasmic sync --config $PWD/plasmic-website.json

7

But now I see that it still creates plasmic.lock instead of plasmic-website.lock which I’d expect. So it still won’t work with multiple plasmic-foo.json files.

8

hmm, yeah :confused:

How would you like to deal with name conflicts? The Plasmic* files should already be in separate folders, but the wrapper files will all go into srcDir. You could edit the file location for each wrapper file to point to a different location so they don’t collide, but it is tedious :confused:

9

Maybe being able to define a prefix per project?