-
-
Notifications
You must be signed in to change notification settings - Fork 23
Open
Description
Currently, Gradle plugin requires stability dump to always be synchronised with the actual Composables in the code, which is a bit of a chore. Ideally, we would want to generate an initial/minimal baseline once and then we would only get alerted when there has been an actual regression in stability.
So, could we get an option to pass stabilityCheck when:
- A composable is removed
- A stable composable is added
- Composable parameters changed, but the new composable is still sable
We would only want the stabilityCheck failing when a change from the baseine resulted in a composable being unstable.
After this is in, there could also be an option to ignore the lack of baseline - even if there is no baseline file present, plugin could still work, it would just always report every single unstable composable in the module (and pass if all are stable).
kunal-jar and adityajar