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

API Composer: merge the clustered data endpoint to be utilized with the viewportData endpoint #281

Open
dancingsushii opened this issue Jun 12, 2024 · 0 comments
Labels
backend Issues related to the data, logic, or communication of the application feature New feature or request
Milestone

Comments

@dancingsushii
Copy link
Contributor

Description

Integrate the functionality of the clustered data endpoint with the viewportData endpoint to optimize data retrieval and reduce the complexity of the API structure.

Acceptance criteria

  • The viewportData endpoint is enhanced to include functionality previously handled by a separate clustered data endpoint.
  • The merged endpoint efficiently delivers both individual and clustered data based on request parameters.

Definition of done (DoD)

  • Component tests have been written and pass
  • All CI tests passed for the pull request
  • Code review has been completed and code has been merged into sprint-release branch
  • All feature branches have been merged and closed
  • New feature code has been documented

DoD general criteria

  • Feature has been fully implemented
  • Feature has been merged into the mainline
  • All acceptance criteria were met
  • Product owner approved features
  • All tests are passing
  • Developers agreed to release
@dancingsushii dancingsushii added backend Issues related to the data, logic, or communication of the application feature New feature or request labels Jun 12, 2024
@dancingsushii dancingsushii added this to the Data lake milestone Jun 12, 2024
@dancingsushii dancingsushii moved this to Product Backlog in amos2024ss04-feature-board Jun 12, 2024
@dancingsushii dancingsushii moved this from Product Backlog to Sprint Backlog in amos2024ss04-feature-board Jun 19, 2024
@dancingsushii dancingsushii moved this from Sprint Backlog to In Progress in amos2024ss04-feature-board Jun 19, 2024
@dancingsushii dancingsushii moved this from In Progress to Product Backlog in amos2024ss04-feature-board Jun 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backend Issues related to the data, logic, or communication of the application feature New feature or request
Projects
Status: Product Backlog
Development

No branches or pull requests

2 participants