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

Fix: Polyline points order (Postgres) #237

Open
2 tasks
elenagensch opened this issue Jan 29, 2022 · 0 comments
Open
2 tasks

Fix: Polyline points order (Postgres) #237

elenagensch opened this issue Jan 29, 2022 · 0 comments
Assignees
Labels
bug Something isn't working
Projects

Comments

@elenagensch
Copy link
Contributor

elenagensch commented Jan 29, 2022

Pre-Context

  • Production Database uses Postgres (not SQLLite)
  • Points that belong to a Polyline are sorted according the point id (e.g. Polyline with pointids:[1,2,3,4,1] is [1,1,2,3,4,] in Postgres)
  • For exporting the polyline to geojson, the first point's coord must be the
  • Currently, the database is not seeded for the ci, these tests fail when the db is seeded: https://github.com/hpi-swt2/compass-portal-red/runs/4840245609?check_suite_focus=true
    -> you can check the fix for adjusting the Polyline geojson logic for Postgres by seeding the ci database

Acceptance criteria

  • seed db in the test and deploy workflow
  • when you display an outer shape the corresponding geojson keeps the order in which the points were added to this polyline
@elenagensch elenagensch self-assigned this Jan 29, 2022
@elenagensch elenagensch added the P5 Priority: Highest label Jan 29, 2022
@elenagensch elenagensch added this to Backlog (Minimum-Limit: 3) in CL Kanban via automation Jan 29, 2022
@elenagensch elenagensch added the bug Something isn't working label Jan 29, 2022
@elenagensch elenagensch removed their assignment Jan 29, 2022
@elenagensch elenagensch moved this from Backlog (Minimum-Limit: 3) to Ready for Dev (Limit: 5) in CL Kanban Jan 29, 2022
@elenagensch elenagensch moved this from Ready for Dev (Limit: 5) to In Development (Limit: 3) in CL Kanban Jan 31, 2022
@elenagensch elenagensch self-assigned this Jan 31, 2022
@cedric-lorenz cedric-lorenz moved this from In Development (Limit: 3) to Ready for Dev (Limit: 5) in CL Kanban Feb 1, 2022
@cedric-lorenz cedric-lorenz removed the P5 Priority: Highest label Feb 1, 2022
@cedric-lorenz cedric-lorenz moved this from Ready for Dev (Limit: 5) to Backlog (Minimum-Limit: 3) in CL Kanban Feb 1, 2022
@rsommerfeld rsommerfeld moved this from Backlog (Minimum-Limit: 3) to Ready for Dev (Limit: 5) in CL Kanban Feb 4, 2022
@rsommerfeld rsommerfeld moved this from Ready for Dev (Limit: 5) to Backlog (Minimum-Limit: 3) in CL Kanban Feb 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
CL Kanban
Backlog (Minimum-Limit: 3)
Development

No branches or pull requests

2 participants