Skip to content

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

Merged
merged 2 commits into from
Dec 6, 2018
Merged

lint non human readable formatters produces invalid output #12936

merged 2 commits into from
Dec 6, 2018

Conversation

alan-agius4
Copy link
Collaborator

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 to BuilderConfiguration

fixes #12674

@alan-agius4 alan-agius4 added the target: major This PR is targeted for the next major release label Nov 12, 2018
@alan-agius4 alan-agius4 changed the title Fix lint format lint non human readable formatters produces invalid output Nov 12, 2018
@filipesilva filipesilva requested a review from hansl November 12, 2018 10:25
@filipesilva
Copy link
Contributor

@hansl is working on the Architect public API and I wonder if these changes run contrary or are subsumed in his plans. @hansl can you have a look?

@hansl
Copy link
Contributor

hansl commented Nov 13, 2018

This looks good. Shouldn't the fix() commit be also part of the patch?

@hansl
Copy link
Contributor

hansl commented Nov 13, 2018

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 projectName be part of the builder configuration, since there's already a projectName in the target spec. @filipesilva what do you think?

@clydin
Copy link
Member

clydin commented Nov 13, 2018

The full project definition should really be made available to the builder. The builder is, after all, acting on the project.

@alan-agius4
Copy link
Collaborator Author

@hans, I didn't mark it as there is also a feat commit since I added a new option to the API

@filipesilva
Copy link
Contributor

@hansl I don't think the builder ever sees the target spec.

@alan-agius4
Copy link
Collaborator Author

Yeah, target spec is not passed to the builders, maybe we should pass this instead?

Also thinking about it, maybe instead of projectName I should name this project for consistence if accepted.

@alan-agius4 alan-agius4 added the needs: discussion On the agenda for team meeting to determine next steps label Nov 15, 2018
@hansl
Copy link
Contributor

hansl commented Nov 19, 2018

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).

@alan-agius4
Copy link
Collaborator Author

Note: Pass TargetSpecifier in BuilderContext

@alan-agius4 alan-agius4 removed the needs: discussion On the agenda for team meeting to determine next steps label Nov 29, 2018
@alan-agius4 alan-agius4 added target: patch This PR is targeted for the next patch release and removed target: major This PR is targeted for the next major release labels Nov 30, 2018
@alan-agius4 alan-agius4 requested a review from hansl November 30, 2018 10:04
@angular angular deleted a comment from ngbot bot Nov 30, 2018
@angular angular deleted a comment from ngbot bot Nov 30, 2018
@ngbot
Copy link

ngbot bot commented Nov 30, 2018

Artifact Baseline Current Change
cli/new-production/test-project/main.js 173.60KB 174.25KB +661 bytes

@angular angular deleted a comment from ngbot bot Nov 30, 2018
@alan-agius4 alan-agius4 added target: patch This PR is targeted for the next patch release and removed target: patch This PR is targeted for the next patch release labels Dec 3, 2018
@alan-agius4 alan-agius4 added target: patch This PR is targeted for the next patch release and removed target: patch This PR is targeted for the next patch release labels Dec 3, 2018
@alexeagle alexeagle merged commit 45b6df5 into angular:master Dec 6, 2018
@alan-agius4 alan-agius4 deleted the fix_lint_format branch December 6, 2018 19:36
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 12, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
target: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The "--format" flag of the "ng lint"-command produces invalid output.
6 participants