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

Implement "unsaved mod defintions" with @inner registry IDs - Slice 2 #9209

Open
BLoe opened this issue Sep 26, 2024 · 0 comments
Open

Implement "unsaved mod defintions" with @inner registry IDs - Slice 2 #9209

BLoe opened this issue Sep 26, 2024 · 0 comments
Assignees
Labels
page editor user experience Improve the user experience (UX)

Comments

@BLoe
Copy link
Collaborator

BLoe commented Sep 26, 2024

  • Change the Add button to New Mod
  • Temporary, "unsaved" mod metadata added to the new component, with id as @inner/mod/<uuid>
    • Don't use the component id as part of the mod id, generate a new uuid, because the component could be moved around and used to create new mods multiple times, and we don't want id collision

Acceptance Criteria

  1. I click Add/New dropdown
  2. I select a starter brick
  3. I see a unsaved mod definition with the starter brick
  4. I add a pipeline to the starter brick
  5. I click the save button (because of slice 1, this only exists at the mod-level)
  6. I see the Save Mod modal
  7. I do not see @inner/mod/<uuid> as the mod id
  8. I see @<my-scope>/.... with the scope dropdown, etc.
  9. I click the save button in the create mod modal
@BLoe BLoe self-assigned this Sep 26, 2024
@BLoe BLoe added page editor user experience Improve the user experience (UX) labels Sep 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
page editor user experience Improve the user experience (UX)
Projects
None yet
Development

No branches or pull requests

1 participant