Get a list of changed components plus all their transitive dependants for testing #236
Replies: 4 comments
-
I like your idea a lot! Thank you @jamesrobson-secondmind I agree, it would be very useful to have this information in a parseable way. I'll think about how to implement it. |
Beta Was this translation helpful? Give feedback.
-
Meanwhile, there are ways to get the changed bricks and use that data in an automated way. This can be used in combination with This is about the actual changed bricks, and won't identify any other bricks using them. I'm looking into that part and will probably add something similar to the things already there (the link). |
Beta Was this translation helpful? Give feedback.
-
@jamesrobson-secondmind I have released a new version that makes it possible to get data for dependent bricks. Announcement here: #244 |
Beta Was this translation helpful? Give feedback.
-
Great, I'll give it a go. |
Beta Was this translation helpful? Give feedback.
-
What I would like is a way to find any component that has changed and walk the tree of imports to find any component that could be affected by the change. This would let you test all code that might have been broken without needing to run everything.
You can almost do this by combining
poly diff
andpoly deps
except thatpoly deps
doesn't provide output in a format that's easy to parse.Beta Was this translation helpful? Give feedback.
All reactions