-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
DependsOn project target does not work as expected #16138
Comments
I have two approaches for solving this:
What do you all think would be a good approach if their is no support for specifying an explicit project and target with DependsOn? |
We are working on this: #16100 The support will only work with the expanded object notation for |
@AgentEnder Awesome! For the time being I built a simple executor that uses the same object notation to build a specific project target. |
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context. |
Current Behavior
Settings DependsOn to a specific project target for my "build:auth-client" does not execute the builds:docs target for my authentication-api project.
Expected Behavior
When setting DependsOn to be "authentication-api:build:docs" I would expect it to execute the target build:docs for the package authentication-api. The format above I was using for depends on is "{PROJECTNAME}:{TARGET}".
For example, if I have my implicitDependencies including my app "authentication-api" I would expect to able to set the depends on project as "authentication-api" and the target "build:docs" explicitly.
GitHub Repo
No response
Steps to Reproduce
Nx Report
Failure Logs
Additional Information
The issue seems to be that DependsOn does not support specifying a specific project and target as a depends on. I may be using the wrong syntax, but I am trying to execute specific project targets when generating my service clients. I have multiple build X Client targets that are formatted as "build:x-client", which each depend on a single projects generated docs. I would like to have the granularity of depending on explicit project targets so that I do not need to build all of my docs for each API to generate one client that only depends on one API.
For example, I have three targets doing the same thing for each API: build:x-client, build:y-client, and build:z-client. If I want to build just my x-client I would expect to be able to depend on x-api and execute build docs instead of being required to build all of the docs for all my dependencies.
The text was updated successfully, but these errors were encountered: