-
Notifications
You must be signed in to change notification settings - Fork 432
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
chore(releases): moving from bundles to releases directory #7500
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Skipped Deployment
|
No changes to documentation |
Component Testing Report Updated Sep 15, 2024 10:05 PM (UTC) ✅ All Tests Passed -- expand for details
|
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.
Great job Jordan, this makes sense to me :)
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.
Thanks for this @jordanl17 !
Looks good to me, would like if we could spend some time debugging the mock issues in a follow up, specially before merging to next
.
This will probably be fixed once we switch to vitest
.
* chore(releases): moving releases/components to releases/tool/components * chore(releases): moving bundles/components to releases/components * chore(releases): moving bundles/hooks to releases/hooks * chore(releases): moving rest of bundles to releases * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): further experimentation on SanityDocumentPreview test failures * chore(releases): fixing ReleaseSummary and Review by mocking components * chore(releases): reverting irrelevent changes
* chore(releases): moving releases/components to releases/tool/components * chore(releases): moving bundles/components to releases/components * chore(releases): moving bundles/hooks to releases/hooks * chore(releases): moving rest of bundles to releases * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): further experimentation on SanityDocumentPreview test failures * chore(releases): fixing ReleaseSummary and Review by mocking components * chore(releases): reverting irrelevent changes
* chore(releases): moving releases/components to releases/tool/components * chore(releases): moving bundles/components to releases/components * chore(releases): moving bundles/hooks to releases/hooks * chore(releases): moving rest of bundles to releases * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): fixing various test imports * chore(releases): further experimentation on SanityDocumentPreview test failures * chore(releases): fixing ReleaseSummary and Review by mocking components * chore(releases): reverting irrelevent changes
Description
Migrating the
core/bundles
directories tocore/bundles
.Note that the methods in these files haven't been changed, only the location of the files.
The directory that previously existed in
core/releases/components
included all the components for the releases plugin (since previouslycore/releases
included only the code for the plugin). This directory has therefore been moved tocore/releases/tool/components
, which feels sensible given that the exports from these components are only used in thetool
directory.What to review
Testing
Tests mostly involved just updating the path for mocks.
However there were particular issues with
ReleasesSummary
andReleasesReview
- for inexplicable reasons, theSanityDefaultPreview
component wasn't receiving it's correct imports, and despite considerable investigation, it seems that there is perhaps a cyclic dependency/mock somewhere which I couldn't track down. Therefore, instead a mock has been added to these 2 tests to cover the issues instead - the tests here are still valid, given that extraneous logic is being mocked and not the parts that are relevant to the testing scope.Notes for release
N/A