Skip to content

Possibility to see affected apps without commiting the code or passing list of changed files #201

@skryvets

Description

@skryvets

Hello everyone.

I posted this question on StackOverflow but didn't get a lot of impressions, since nx is a very specific to certain type of projects. Currently, I do some proof of concept and want to research all options which are available in nx and hope to get some insights here.

Prerequisites:

One of the most powerful features of NX is to able to see which Angular applications are affected by the recent change.

However, in order to make it work documentation tells that you need:

  1. Provide SHA's of two commits: npm run apps:affected -- SHA1 SHA2 OR
  2. Specify each file that has been changed and pass them as parameters: npm run apps:affected -- --files="libs/mylib/index.ts,libs/mylib2/index.ts"

Obviously, the first option doesn't feet as I don't want to commit my changes and see what's broken. The second option doesn't work as well because it really requires a lot of effort to pass each changed file as a parameter.

Question:

Is there a way that I can change a file in a lib and see what apps are affected without passing the commit SHA or manually specifying each change? (probably just by analyzing git diff).

Thank you!

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions