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
[Bug] Crash because of Roomfinder Maps data for Z10 #122
Comments
Preliminary triage results: This is a data issue. I will continue after a sort break |
The issue was in {
"maps": [
["200000", 54, "M\u00fcnchen", 640, 603],
["400000", 156, "M\u00fcnchen und Umgebung", 420, 515],
["100000000", 9, "Weltkarte Norden", 1619, 396]
],
"default_map": ["4000", 12, "Stammgel\u00e4nde Basiskarte", 501, 484]
} FYI: |
A case very similar to this keeps happening at https://nav.tum.sexy/building/2930 though |
Signed-off-by: Frank Elsinga <frank@elsinga.de>
I had some old version of the website in my cache. |
No, Frank this is wrong. Thanks @joschahenningsen for the report ❤️ Error Message:
|
Apperantly we dont clean the maps default, if no maps are available: "maps": {
"roomfinder": {
"available": [],
"default": "rf12"
},
"default": "interactive"
}, @octycs what would be the expected case if no maps are available for an eintity: "maps": {
"roomfinder": {
"available": [],
"default": null
},
"default": "interactive"
}, or "maps": {
"default": "interactive"
}, |
I think the latter is better. This is what the webclient currently expects as well (https://github.com/TUM-Dev/navigatum/blob/main/webclient/src/views/view/view-view.js#L155) |
Describe the bug
Z10 (and potentially other entries) have an error in the Roomfinder Maps data.
To Reproduce
Steps to reproduce the behavior:
TypeError: view_data.maps.roomfinder.available[state.map.roomfinder.selected_index] is undefined
Expected behavior
Should not crash
Additional context
This is a crash in the frontend (which shouldn't happen), but probably related to an error in the data.
The text was updated successfully, but these errors were encountered: