Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: stringify yes and no map keys #379

Merged
merged 1 commit into from
Jul 30, 2020
Merged

fix: stringify yes and no map keys #379

merged 1 commit into from
Jul 30, 2020

Conversation

kjessec
Copy link
Contributor

@kjessec kjessec commented Jul 30, 2020

Summary of changes

In swagger definition, TallyResult response properties has yes and no as map keys. These are treated respectively true and false in yaml spec (🤷‍♂️) . This makes spec compliant go yaml parser scream, as in golang maps cannot have bool type as keys.

Report of required housekeeping

  • Github issue OR spec proposal link
  • Wrote tests
  • Updated relevant documentation (docs/)
  • Added a relevant changelog entry: clog add [section] [stanza] [message]

(FOR ADMIN) Before merging

  • Added appropriate labels to PR
  • Squashed all commits, uses message "Merge pull request #XYZ: [title]" (coding standards)
  • Confirm added tests are consistent with the intended behavior of changes
  • Ensure all tests pass

@kjessec kjessec added bug Something isn't working client rest / cli code improvements labels Jul 30, 2020
@kjessec kjessec requested review from hanjukim and yun-yeo July 30, 2020 05:28
Copy link
Contributor

@yun-yeo yun-yeo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@yun-yeo yun-yeo merged commit 1b24b92 into develop Jul 30, 2020
@yun-yeo yun-yeo deleted the fix-swagger-yaml branch July 30, 2020 07:46
yun-yeo pushed a commit that referenced this pull request Aug 4, 2020
yun-yeo pushed a commit that referenced this pull request Sep 22, 2020
* add columbus-4 genesis migration script

* implement indicators querier for tax rate update

* add public option at starting rest-server & enforce to use tx.height option when public option is on

* fix(treasury): indicator endpoint
feat(treasury): indicator swagger definition

* fix: stringify yes and no map keys (#379)

* change module account name & permission key

* apply core module migration script

* add pretty optiong

* add new modules: msgauth, wasm, mint to script

* update script for wasm params and expected time

* remove wasm gas_multiplier params from genesis migration script

* add changelog

Co-authored-by: Paul Kim <[email protected]>
Co-authored-by: Jesse Chung <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working client rest / cli code improvements
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants