Cleanup schema and split nuxt 2 types
refactor(nuxt)!: cleanup schema and split nuxt 2 types (#8487)
Cleanup schema and split nuxt 2 typesrefactorcleanup schema split nuxt types
Committed by pi0
commit message
refactor(nuxt)!: cleanup schema and split nuxt 2 types (#8487)Editor assessment
Breaking refactors demand the most communication, and this message signals the breaking part correctly with '!' after refactor(nuxt), but stops there. The subject 'cleanup schema and split nuxt 2 types' hints at the substance — Nuxt 2 type definitions separated out — yet per the spec's spirit a BREAKING CHANGE footer should spell out what consumers must do: which types moved, to which import paths, and what breaks if untouched. Without it, the major bump is inferable but unmigratable from the log alone. Style mechanics are otherwise fine: imperative, lowercase, period-free, with (#8487) for context.