-
Notifications
You must be signed in to change notification settings - Fork 31
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
api/schema: Fix API schema after API reference refactor #1720
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
229eb38
to
7ce428e
Compare
Also deleted an even older test.json file lol
Will be helpful for debugging
Codecov Report
@@ Coverage Diff @@
## master #1720 +/- ##
=============================================
Coverage 53.61029% 53.61029%
=============================================
Files 75 75
Lines 5055 5055
Branches 1008 1008
=============================================
Hits 2710 2710
Misses 2001 2001
Partials 344 344 see 1 file with indirect coverage changes Continue to review full report in Codecov by Sentry.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@@ -1,6 +1,6 @@ | |||
import Ajv from "ajv"; | |||
import pack from "ajv-pack"; | |||
import { safeLoad as parseYaml } from "js-yaml"; | |||
import { safeLoad as parseYaml, safeDump as serializeYaml } from "js-yaml"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is safeDump
supposed to be imported?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah it's used to write the merged yaml now!
What does this pull request do? Explain your changes. (required)
On the API reference refactor we created new schema files but forgot to delete
the old one, so it was able to merge cleanly even though it had conflicts with master.
This was caused by a couple other conflicting changes to the schema. Specifically:
Specific updates (required)
How did you test each of these updates (required)
yarn test
Does this pull request close any open issues?
No.
Checklist