feat(scully): adding support for project.json with no angular.json or workspace.json #1654
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Currently, individual
project.json
files in each app are supported but scully still looks for the project path in eitherworkspace.json
orangualr.json
and expects theprojects
object to exist. With the latest versions of Nx all the project configs have been migrated into the app folders andworkspace.json
&angular.json
are removed.Issue Number: #1520
What is the new behavior?
If there is no
projects
object inangular.json
orworkspace.json
scully will then look forproject.json
is theapps/[project]
folder.Does this PR introduce a breaking change?
Other information