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

Migrate Current Store Service to Signal Store #30020

Closed
Tracked by #30012
oidacra opened this issue Sep 16, 2024 · 3 comments · Fixed by #30201
Closed
Tracked by #30012

Migrate Current Store Service to Signal Store #30020

oidacra opened this issue Sep 16, 2024 · 3 comments · Fixed by #30201

Comments

@oidacra
Copy link
Member

oidacra commented Sep 16, 2024

Parent Issue

#30012

Task

Migrate the current store service to Signal Store, maintaining all existing functionalities while preparing for future flexibility and considering component states.

Proposed Objective

Technical User Experience

Proposed Priority

Priority 2 - Important

Acceptance Criteria

  1. Implement Signal Store to replace the current store service
  2. Migrate all existing functionalities from the current store to Signal Store
  3. Ensure all components currently using the store are updated to use Signal Store
  4. Implement state management for component-level states using Signal Store
  5. Design the Signal Store structure to be flexible for future additions and modifications
  6. Add unit tests to cover all Signal Store functionalities
@oidacra oidacra changed the title Migrate to Signal Store Migrate Current Store Service to Signal Store Sep 16, 2024
@oidacra oidacra moved this from New to Next 1-3 Sprints in dotCMS - Product Planning Sep 18, 2024
@oidacra oidacra self-assigned this Sep 26, 2024
@oidacra oidacra moved this from Next 1-3 Sprints to In Progress in dotCMS - Product Planning Sep 26, 2024
@oidacra oidacra linked a pull request Oct 2, 2024 that will close this issue
3 tasks
@oidacra oidacra moved this from In Progress to In Review in dotCMS - Product Planning Oct 2, 2024
@github-project-automation github-project-automation bot moved this from In Review to Internal QA in dotCMS - Product Planning Oct 8, 2024
@oidacra
Copy link
Member Author

oidacra commented Oct 8, 2024

QA Notes:

Objective

Verify functionality after migrating to Signal Store. This is just for the new Edit Contentlet

Tests

Create content

  • Create new content in a ContentType
  • Verify it saves correctly

View content

  • Open existing content
  • Check that all information is displayed

Edit content

  • Modify existing content
  • Save changes and verify they are applied correctly

Success criteria

  • All functions work without errors
  • No existing functionality is lost

@dsilvam dsilvam assigned dsilvam and unassigned oidacra Oct 8, 2024
@dsilvam
Copy link
Contributor

dsilvam commented Oct 8, 2024

Passed IQA: All test cases from the comment working.

Categories are not able to be saved but it is not related to this and was captured on a different card #30204

@dsilvam dsilvam moved this from Internal QA to QA - Backlog in dotCMS - Product Planning Oct 8, 2024
@josemejias11 josemejias11 moved this from QA - Backlog to QA - In Progress in dotCMS - Product Planning Oct 8, 2024
@josemejias11
Copy link
Contributor

Approved: Tested on trunk_e0e83bd, Docker, macOS 14.5, FF v126.0.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment