Skip to content
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

affected:lint --file option #1535

Closed
4 tasks done
JochenDiekenbrock opened this issue Jun 28, 2019 · 2 comments · Fixed by #1834
Closed
4 tasks done

affected:lint --file option #1535

JochenDiekenbrock opened this issue Jun 28, 2019 · 2 comments · Fixed by #1834

Comments

@JochenDiekenbrock
Copy link

Prerequisites

  • I am running the latest version
  • I checked the documentation and found no answer
  • I checked to make sure that this issue has not already been filed
  • I'm reporting the issue to the correct repository (not related to Angular, AngularCLI or any dependency)

Expected Behavior

https://nx.dev/api/npmscripts/affected-lint mentions a --file option, but yarn affected:lint --all --file=.vis/output.json results in the message Unknown option: '--file for each app.

yarn affected:lint --help does not show this option.

Is this a bug or a mistage in https://nx.dev/api/npmscripts/affected-lint?

How would I use yarn affected:lint to create either one checkstyle format file for the complete workspace or one checkstyle format file for each app?

Failure Information (for bugs)

Please help provide information about the failure if this is a bug. If it is not a bug, please remove the rest of this template.

Steps to Reproduce

Please provide detailed steps for reproducing the issue.

  1. setup a new workspace
  2. call yarn affected:lint --help

Context

Please provide any relevant information about your setup:

  • version of Nx used: 8.2.0
  • version of Angular CLI used: Angular CLI: 8.0.0
  • angular.json configuration
  • version of Angular DevKit used: 8.0.1
@FrozenPandaz
Copy link
Collaborator

FrozenPandaz commented Jun 28, 2019

Thank you for reporting this issue.

This seems like a bug in our documentation generation. @bcabanes can you take a look please?

bcabanes added a commit to bcabanes/nx that referenced this issue Sep 12, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close nrwl#1535
bcabanes added a commit to bcabanes/nx that referenced this issue Sep 12, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close nrwl#1535
bcabanes added a commit to bcabanes/nx that referenced this issue Sep 12, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close nrwl#1535
bcabanes added a commit to bcabanes/nx that referenced this issue Sep 12, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close nrwl#1535
vsavkin pushed a commit that referenced this issue Sep 17, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close #1535
Doginal pushed a commit to Doginal/nx that referenced this issue Oct 30, 2019
Update the description of the `--files` options for the `affected`
command, making it clearer (hopefully).

close nrwl#1535
@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 25, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants