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(certificates) return proper format for GET /certificates route #2463

Closed
wants to merge 1 commit into from

Conversation

p0pr0ck5
Copy link
Contributor

Summary

GET /certificates was originally built with some custom logic for the certificate <-> snis object relationship, and as such did not use the paginated set helper used by most GET routes. This commit updates the response object to resemble that of other retrieval functions (as well as match the return format specified in the documentation).

Full changelog

  • fix(certificates) return proper format for GET /certificates route

Issues resolved

Fix #2462

@subnetmarco subnetmarco added pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release) and removed pr/status/please review labels Apr 28, 2017
@p0pr0ck5
Copy link
Contributor Author

p0pr0ck5 commented Apr 28, 2017

@thibaultcha i know you had reservations on merging this into master; thoughts?

@p0pr0ck5 p0pr0ck5 force-pushed the fix/certificates-get branch 2 times, most recently from 803af57 to 26f91b0 Compare April 28, 2017 16:37
@p0pr0ck5 p0pr0ck5 force-pushed the fix/certificates-get branch from 26f91b0 to cc8697d Compare April 28, 2017 16:42
@thibaultcha
Copy link
Member

@p0pr0ck5 It's indeed not aligned with the documentation, so as much as this might be considered a breaking change, I made up my mind and do think it should be merged as well :) Will include it in 0.10.2, thanks for the hotfix! 😉

@thibaultcha
Copy link
Member

Merged to release/0.10.2 with some edits.

@thibaultcha thibaultcha deleted the fix/certificates-get branch April 28, 2017 17:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr/ready (but hold merge) No more concerns, but do not merge yet (probably a conflict of interest with another PR or release)
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Certificates has an inconsistent payload when empty
3 participants