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

api/schema: Fix API schema after API reference refactor #1720

Merged
merged 15 commits into from
May 8, 2023

Conversation

victorges
Copy link
Member

@victorges victorges commented May 8, 2023

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:

  • stream health
  • recordings v2
  • creator ID
  • multi-participant (room abstraction&endpoints)

Specific updates (required)

  • Added all those lost updates
  • Went through those moving private stuff to db-schema

How did you test each of these updates (required)

  • Compared old and new generated schemas throughout all the [dev] commits here
  • yarn test

Does this pull request close any open issues?
No.

Checklist

  • I have read the CONTRIBUTING document.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have added tests to cover my changes.

@vercel
Copy link

vercel bot commented May 8, 2023

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
livepeer-studio ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 8, 2023 8:35pm

@victorges victorges changed the title Vg/fix/api schema api/schema: Fix API schema after API reference refactor May 8, 2023
@victorges victorges marked this pull request as ready for review May 8, 2023 20:15
@victorges victorges requested a review from a team as a code owner May 8, 2023 20:15
Also deleted an even older test.json file lol
@codecov
Copy link

codecov bot commented May 8, 2023

Codecov Report

Merging #1720 (47945ef) into master (b959d4e) will not change coverage.
The diff coverage is n/a.

Impacted file tree graph

@@              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.

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

see 1 file with indirect coverage changes

Copy link
Member

@gioelecerati gioelecerati left a 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";
Copy link
Member

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?

Copy link
Member Author

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!

@victorges victorges merged commit 1c0773d into master May 8, 2023
12 checks passed
@victorges victorges deleted the vg/fix/api-schema branch May 8, 2023 21:09
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.

None yet

2 participants