Skip to content

docs(openapi): Fix documented response code #227

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

Merged
merged 1 commit into from
Jun 16, 2020

Conversation

mikecdavis
Copy link
Contributor

@mikecdavis mikecdavis commented May 20, 2020

Summary

The current API spec is out of date with the existing implementation. /track returns an HTTP 200 and not a 204. The change was made as part of this commit, but the spec was not updated.

The current API spec is out of date with the existing implementation. `/track` returns an HTTP 200 and not a 204. The change was made as part of [this](70300ad#diff-792ff1ebb42545c5d3e4b34233906b27L75-R70) commit, but the spec was not updated.
@codecov
Copy link

codecov bot commented May 20, 2020

Codecov Report

Merging #227 into master will not change coverage.
The diff coverage is 100.00%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master     #227   +/-   ##
=======================================
  Coverage   82.55%   82.55%           
=======================================
  Files          27       27           
  Lines        1261     1261           
=======================================
  Hits         1041     1041           
  Misses        165      165           
  Partials       55       55           
Impacted Files Coverage Δ
pkg/optimizely/client.go 80.00% <100.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 573c10d...6c05bfe. Read the comment docs.

@mikeproeng37 mikeproeng37 merged commit d28da69 into master Jun 16, 2020
@mikeproeng37 mikeproeng37 deleted the mikecdavis/update-api-spec branch June 16, 2020 02:46
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.

3 participants