Replies: 5 comments
-
This may be related to a scenario I'm researching! My workspaces are contained in
I would like to do something like:
|
Beta Was this translation helpful? Give feedback.
This comment has been minimized.
This comment has been minimized.
-
I've renamed this issue to more generally be about wildcarding, even though the original issue was specifically about using directory paths, rather than package names in the task definitions. |
Beta Was this translation helpful? Give feedback.
-
Should we support single asterisk notation? If so, there could be a collision with: #4145 |
Beta Was this translation helpful? Give feedback.
-
#4145's proposed solution may conflict, that's a good call out, but I think that issue is asking for a general "finalization" API. I think that could be a good feature as well, and we should take that into account when designing the API. The next step would be to outline the scope of this API and (as @psychobolt mentioned) where it could overlap with other features. Off the top of my head,
It could overlap with:
|
Beta Was this translation helpful? Give feedback.
-
Describe the feature you'd like to request
We have two main types of workspaces in our monorepo: packages and microfrontends. These two types each require different
dependsOn
configurations, but from what I can see in the documentation this is not possible to do.Describe the solution you'd like
I propose being able to use the new
--filter
syntax in the Pipeline name configs:Describe alternatives you've considered
It would be nice to at the very least have globs work in the names:
@mf/*#build
. Then we could name every workspace differently to handle these cases.Another option would be to not require every string in
dependsOn
to match a file, then any missing files would be hashed as empty or something similar.Beta Was this translation helpful? Give feedback.
All reactions