fix: stringify yes and no map keys #379
Merged
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 of changes
In swagger definition,
TallyResult
response properties hasyes
andno
as map keys. These are treated respectivelytrue
andfalse
in yaml spec (🤷♂️) . This makes spec compliant go yaml parser scream, as in golang maps cannot havebool
type as keys.Report of required housekeeping
(FOR ADMIN) Before merging