You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 10, 2024. It is now read-only.
implementing the more information nav.tum.sexy/api/get/:id api-endpint (replacing the current endpoit)
implementing the search nav.tum.sexy/api/search?q=querry api-endpoint (replacing the current endpoit)
Optional:
5. implement the feedback api
All of these steps require the previous step to be completed, to work to the full extend possible, but dont require any of the further steps to be completed to be shipped (except, that once 3 is done, 1. will become unnessesary and we may want to remove this code).
We have renamed some rooms in the roomfinder, but those are edgecases, that I assume most of our users will not notice.
The text was updated successfully, but these errors were encountered:
CommanderStorm
changed the title
Migrate the Roomfinder to [NavigaTUM](https://github.com/TUM-Dev/navigatum)
Migrate the Roomfinder to NavigaTUM
May 26, 2022
Sorry for the long delay: @kmodexc is working on #1437, but this will take a bit longer, since we are currently in the middle of the semester and stuff is a bit stressful currently. #1437 is a bigger issue than initial anticipated 😉
Help with 3,4 would be greatly appreciated. ❤️
There are two stopgap solutions until #1437 is properly done I can imagine (one is more work, one is less), since until then we won't have an interactive map.
Currently the used roomfinder has a few problems. Namely #1338, #1337, #1182 and #415
A migration to NavigaTUM could solve some of these problems.
The suggested plan to fix this would be:
nav.tum.sexy/api/get/:id
api-endpint (replacing the current endpoit)nav.tum.sexy/api/search?q=querry
api-endpoint (replacing the current endpoit)Optional:
5. implement the feedback api
All of these steps require the previous step to be completed, to work to the full extend possible, but dont require any of the further steps to be completed to be shipped (except, that once 3 is done, 1. will become unnessesary and we may want to remove this code).
We have renamed some rooms in the roomfinder, but those are edgecases, that I assume most of our users will not notice.
You can find our api documentation at https://editor.swagger.io/?url=https://raw.githubusercontent.com/TUM-Dev/navigatum/main/openapi.yaml
If you find any dificultys/anything is unclear/you found a bug, please feel free to open an issue.
The text was updated successfully, but these errors were encountered: