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

Backend changes for Segment redesign #2085

Closed
amurphy-cl opened this issue Oct 29, 2024 · 0 comments · Fixed by #2145
Closed

Backend changes for Segment redesign #2085

amurphy-cl opened this issue Oct 29, 2024 · 0 comments · Fixed by #2145
Assignees

Comments

@amurphy-cl
Copy link
Collaborator

amurphy-cl commented Oct 29, 2024

Make backend changes to support Segment design refresh

Old segment structure doc: https://docs.google.com/document/d/1IxFuCt_UGGyq9zynPTO9ubhWyKk5vo7UYupPIzNJEKI/edit?tab=t.0#heading=h.k7a8qo328l3s

Changes from old to new
For new segments: we won't have the three categories e.g. individual, group, and sub-segment. Instead we will only have sub-segments.

  • New endpoint for new list - This will create a new private segment and add it to the subSegments array of the parent public segment. The new private segment will have a defined 'listType' attribute. It should be a segment edit with the private subsegment creation as part of the transaction
  • New endpoint to delete a list - delete the record for the list and remove it from the parent segment's 'subsegments` array
  • Database schema migration to add an optional 'listType' string attribute.

NB: creating/deleting/editing a new segment should be able to use the existing endpoints.

@amurphy-cl amurphy-cl added this to the Program Increment PI14 milestone Oct 29, 2024
@amurphy-cl amurphy-cl moved this to Refined ToDo in UpGrade Project Nov 6, 2024
@bcb37 bcb37 self-assigned this Nov 6, 2024
@bcb37 bcb37 linked a pull request Dec 2, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: In Progress
Development

Successfully merging a pull request may close this issue.

2 participants