-
Notifications
You must be signed in to change notification settings - Fork 12k
lint non human readable formatters produces invalid output #12936
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
Conversation
This looks good. Shouldn't the |
Actually, I think this feature is not something we want. Why not use the projectName that's used to call the linter? Seems like an anti-pattern we should not promote to have the |
The full project definition should really be made available to the builder. The builder is, after all, acting on the project. |
@hans, I didn't mark it as there is also a feat commit since I added a new option to the API |
@hansl I don't think the builder ever sees the target spec. |
Yeah, target spec is not passed to the builders, maybe we should pass this instead? Also thinking about it, maybe instead of |
Yeah it should definitely not be an option. We should find a way to pass that in (the new Architect API will pass in the project and the workspace). |
Note: Pass TargetSpecifier in BuilderContext |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
refactor(@angular/cli): move project name being linted logic to builder
fix(@angular-devkit/build-angular): lint non human readable formatters produces invalid output
feat(@angular-devkit/architect): add
projectName
toBuilderConfiguration
fixes #12674