graphql-hive / graphql-hive/console
Feature Request: Display "Dangerous Changes" as a Separate Category from "Breaking Changes" in Hive UI
- Dominant language
- TypeScript
- Stars
- 483
- Forks
- 145
- Avg merge
- 2d 5h
- Merged PRs (30d)
- 65
Description
Hello!
**Problem**
The Hive UI currently displays dangerous changes under "Breaking Changes", which is misleading and inconsistent with the CI validation output where its correctly separated from breaking changes. This mislabeling in the UI causes confusion about the actual severity and nature of the schema changes being reviewed.
**Request**
Display "Dangerous Changes" as its own distinct section in the Hive UI, separate from "Breaking Changes", matching the CI validation output.
**Nice to Have**
Add an information symbol (ℹ️) next to "Dangerous Changes" (similar to "Breaking Changes") to explain what constitutes a dangerous change and how it differs from a breaking change.
Contributor guide
Assessment
This issue has not been assessed yet.