-
Notifications
You must be signed in to change notification settings - Fork 451
-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Module improvement tracking issue #2252
Comments
I am definitely interested in seeing modules fleshed out a bit more. I'm coming from being a fairly heavy make user where our team could organize make 'stubs' and include them on a per-repo basis. Something like this was nice and handy in Make-land, and is definitely nearly there with Just
The recipe naming with the This has made it difficult to fully embrace modules, so we resort to using imports in Just and doing a more 'restrictive' faux-namespacing in the recipe names. I would therefore +1 all the following, as I think they all contribute
As an aside, I think I'd be perfect happy as well if recipe names could include some special characters that allow the 'faux' namespacing I mention, |
Adding this one to the list: #2271 |
We have nested just mods that goes:
Which allows us to call However from How exactly could I call a local task, without using the hierarchy? To highlight the issue in a different way: I have a parent git repo, which has git submodules. Each submodule I wish to have a Eg When running
But when I include it in a monorepo, and try to expose its tasks to a parent Justfile
|
I have put some thought into this. Should calls to just defined in a nested module not default to recipes in the current file, and then navigate up until it finds a recipe that matches? Why does a submodule need to be aware of its location in the module hierarchy? And similarly you can should be able to call a dependancy to a module, relative to the currently module hierarchy. ie Given
In deploy env="dev": (stack/deploy env)
# or
deploy env="dev":
just stack deploy {{env}}
# not
deploy env="dev":
just iac docker stack deploy {{env}} Not, as "docker/mod.just" would now have to know that it resides in iac, and can be installed anywhere else but in that exact hierarchy. |
This issue tracks improvements and missing features of submodules
.env
filesjust --show
work with modulesThis thread should probably be used for general discussion. If you're interested in one of the above features, mention it in this thread and I'll create a dedicated issue for it.
The text was updated successfully, but these errors were encountered: