chore: sync OpenAPI spec, change_status gains Failed - #84
Merged
Merged
Conversation
Change and change-event items now document a sixth change_status value, Failed. The vendored spec keeps the detail_url field on AlertInfo and AlertItem, which the upstream spec does not carry yet.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Re-syncs the vendored OpenAPI spec from flashduty-docs and regenerates the models.
ChangeItem.change_statusandChangeEventItem.change_statusgain the enum valueFailed(en + zh spec, doc comment inmodels_gen.go).detail_urlonAlertInfo/AlertItemis kept. The upstream spec does not list it yet, so a raw sync would have removed a field that v0.15.6 / v0.15.7 already ship.Verification
make sync-specoutput is byte-identical to flashduty-docs main before thedetail_urlhunks are re-applied.make generate,make test(race),make buildpass locally.