-
Notifications
You must be signed in to change notification settings - Fork 12
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
Make a fallback config-file hard coded #208
Labels
0 bug
Something isn't working
Comments
Summery of the done works
The error messages
The hard coded config{
"map": {
"location": {
"lat": 50.8129,
"lng": 5.6030,
"zoom": 6
},
"colorStyle": MapColorModes.GRAY
},
"popularTags": {
"min_count": 2
},
"sidebar": {
"title": "Kartevonmorgen"
}
} |
@alex0107 please deplay the realease: https://github.com/kartevonmorgen/kartevonmorgen.ts/releases/tag/v1.2.3 |
It seems, that all instabilities are solve https://status.rhw24.it/status/allgemein |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
The Map App is stopping. One reason could be, that the config file cant get loaded,
Maybe the config file in the nextcloud is blocked by nextcloud, because the nextcloud is using/syncing the file.
But that is a bad implementation as an App should not crush completly, just because an API or a config file is not availiabl.
Solution:
Implement a hard codes version of the config file directly in the App, which gets loaded, if no other config file cant be found in a certain time.
Use the values from the main file for this implementation: https://www.kartevonmorgen.org/public/projects/main/config.json
To Reproduce
happens sometimes, you never know when...
Expected behavior
stable loading of the map-app. If an API or file is unavalible I expect a popup or an error message.
Screenshots
Additional context
The Backend got an update In the beginning of April, so the backend shouldnot be the reason for the bug.
Increasing the timeout is also part of the solution: #207
The text was updated successfully, but these errors were encountered: