Do it once, commit the json config to your source control and you’re done. Not sure how much simpler we can get than native IDE support? You could write a script to generate the workspace config file if you want.
cmo
byu
Wow, something like this-- the dependency checks, and boundary enforcement-- could help my organization’s goal in wrangling the various project repos, to get back to one monorepo.
Question: How well does this work with umbrella apps? Any special considerations or notes?
ie. most project repos are individual apps, but there exists one umbrella app. We were thinking of migrating all other projects under the umbrella.
0
pnezis
Question: How well does this work with umbrella apps? Any special considerations or notes?
ie. most project repos are individual apps, but there exists one umbrella app. We were thinking of migrating all other projects under the umbrella.
It will not work with umbrellas since it is an umbrella alternative. You can move all umbrella apps out of the umbrella in any folder you wish, and it will work.
0
mindreframer
Hey @cmo, I’m trying to use workspaces, and ElixirLS is only picking up the top-level folder. Packages in nested folder are not recognized. Do you have any extra configuration to make it work?
.code-workspace - file:
{
"folders": [
{
"path": ".",
"name": "root"
},
{
"path": "packages/package_a"
}
],
}
Modules in package_a are not loaded in ElixirLS.
0
mindreframer
It seems to work, when I include 2 subfolders. I get 2 ElixirLS processes, one for each elixir folder. But including the top-folder also into workspaces seems to confuse ElixirLS
0
cmo
Yes, exclude the top level folder. Mine is just:
{
"folders": [
{
"name": "a",
"path": "a"
},
{
"name": "b",
"path": "b"
},
],
"settings": {
"workbench.colorCustomizations": {}
}
}
0
pnezis
@cmo Although quoting works I would suggest to pass the task arguments after the return separator --. This way you will avoid escaping quotes. Thanks for bringing this up, I will update the docs accordingly.
mix workspace.run -t deps.update -- --all
Regarding the common deps path I have not included this in purpose, I don’t want to enforce any conventions. But you are right that a mention in the docs about the various options regarding the build artifacts folders would help. I will try to find an appropriate wording and will add it.
1
cmo
I did try that but
mix workspace.run -t deps.update -- --all ─╯
==> nimble_options
Compiling 3 files (.ex)
Generated nimble_options app
==> cli_options
Compiling 5 files (.ex)
Generated cli_options app
==> workspace
Compiling 42 files (.ex)
Generated workspace app
** (CliOptions.ParseError) invalid option "all"
(cli_options 0.1.0) lib/cli_options.ex:410: CliOptions.parse!/2
(workspace 0.1.0) lib/mix/tasks/workspace.run.ex:225: Mix.Tasks.Workspace.Run.run/1
(mix 1.16.2) lib/mix/task.ex:478: anonymous fn/3 in Mix.Task.run_task/5
(mix 1.16.2) lib/mix/cli.ex:96: Mix.CLI.run_task/2
c:/Users/simon/scoop/apps/elixir/current/bin/mix:2: (file)
edit: it’s a powershell thing I guess. Works in cmd 
0
pnezis
edit: it’s a powershell thing I guess. Works in
cmd
Strange, I will need to find a windows machine to debug 
0