Skip to content

ensure constant client response body order#848

Merged
casualjim merged 1 commit intogo-swagger:masterfrom
Exient:846-stable-gen-order
Jan 7, 2017
Merged

ensure constant client response body order#848
casualjim merged 1 commit intogo-swagger:masterfrom
Exient:846-stable-gen-order

Conversation

@GlenDC
Copy link
Copy Markdown
Member

@GlenDC GlenDC commented Jan 7, 2017

fixes #846

Also added a unit test to ensure the order of the Response & Body (payload).

Using a new swagger build with these changes, it now seems to appear that the order of generated objects is constant across sequential generations. Tested it for both the client and server of the EVE API Spec referenced in #846. Locally it seems to hold up, as it seemed to be only the body (extraSchemes) that were not sorted yet. Therefore I only added a unit-test to test the order of the body, as mentioned earlier.

@codecov-io
Copy link
Copy Markdown

Current coverage is 69.28% (diff: 100%)

Merging #848 into master will increase coverage by 0.02%

@@             master       #848   diff @@
==========================================
  Files            21         21          
  Lines          5863       5864     +1   
  Methods           0          0          
  Messages          0          0          
  Branches          0          0          
==========================================
+ Hits           4061       4063     +2   
+ Misses         1389       1388     -1   
  Partials        413        413          

Powered by Codecov. Last update a04692f...ce5525d

@casualjim casualjim merged commit 7b1ab59 into go-swagger:master Jan 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

responses dont have a stable order

3 participants