-
Notifications
You must be signed in to change notification settings - Fork 22
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
Feature - Remove standalone mods phase 5 - slices 1+2 #9123
Conversation
Playwright test results 10 failed Details Open report ↗︎ Failed testschrome › tests/pageEditor/addStarterBrick.spec.ts › Add new mod with starter bricks Flaky testsmsedge › tests/modLifecycle.spec.ts › create, run, package, and update mod Skipped testschrome › tests/runtime/googleSheetsIntegration.spec.ts › can activate a google spreadsheet mod with config options |
3956ee7
to
5598eca
Compare
Yeah that's definitely a gap that I missed from the spec then, if the save button on mods is not supposed to be hidden at all now. Sorry! |
Discovering a blocking issue with clearing/resetting a mod: https://www.loom.com/share/c08fb2d00c27429cb310b9907440115c |
@@ -1,7 +1,7 @@ | |||
apiVersion: v3 | |||
kind: recipe | |||
metadata: | |||
id: '@extension-e2e-test-unaffiliated/test-mod-created-with-button' | |||
id: '@extension-e2e-test-unaffiliated/00000000-0000-0000-0000-000000000000' |
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.
Why are all these ids identical now? Does that matter at all?
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.
This is actually how snapshots used to be/should look like. The real ids are actually random unique uuids. The snapshot comparison I think takes care of matching the specific uuid (@fungairino I don't know exactly what handles that, but that's what is going on yes?). Your original test was using identical ids causing test collision.
* wip * better paths type and updated readme * update types * fix type error
* Update snapshots
* log successful trigger runs to debug instead of info * update comment * added logging and a quick rename * disable idb logging feature flag * fix test --------- Co-authored-by: Graham Langford <[email protected]>
* refactor/extract duplicated functions; create syncActivatedModCOmponents * run team trial updater in the background * fix modUpdater test, create deactivateMod test * create initial data model * finish implementing transformers * fix typing * remove dead code * switch back to LegacyUserRole and change organization.role to organization.isAdmin * remove dead code; use UserRole * remove the lifted value from Organzation * rename OrganizationMembers -> OrganizationMemberships * member -> membership * update typings * adds deactivateModComponent tests * organization -> team * rename all service layer level organization types to ream * rename local variables
* adding timeout to sweep and blocked handling * improve inclusivity
What does this PR do?
Remaining Work
_recipe
field refactoring to accomplish as a separate DX taskFor more information on our expectations for the PR process, see the
code review principles doc