Remove deprecated "submission" ScheduleItem type - #4805
Open
marcoacierno wants to merge 2 commits into
Open
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
Removes the deprecated
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4805 +/- ##
==========================================
- Coverage 93.11% 93.11% -0.01%
==========================================
Files 360 360
Lines 11239 11236 -3
Branches 905 904 -1
==========================================
- Hits 10465 10462 -3
Misses 663 663
Partials 111 111 🚀 New features to boost your workflow:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
submissionis no longer used and has been replaced with talk, tutorial, panel etc.The FE used this
talksquery that didn't work while the detail itself worked as it usedtalk(which queries all schedule items). We likely don't need to pre-render the event pages every deploy and can rely on the node server rendering them on demand like it is doing right now anyway