graphql-hive / graphql-hive/console
Don't flag dangerous changes on 0-usage types
Open
- Dominant language
- TypeScript
- Stars
- 483
- Forks
- 145
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 65
Description
Right now if you make a dangerous change (e.g. adding an enum value) to a type with 0 usage, validation for dangerous changes will fail. It should instead be marked safe based on usage.
Contributor guide
Assessment
This issue has not been assessed yet.