When a resource is named config.json, it will result in a conflict with our local config.json file upon refreshing the page displaying that resource.
We cshould improve the handler regex in n inmanta-ui for this. However, we made it this liberal so that it works for any view in the SPA. the regex needs to be adjusted, probably with a $ at the end of it.
LukasStordeur
commented
1 month ago
See thread : https://inmanta.slack.com/archives/C045Y42N49W/p1721317870833269
When a resource is named config.json, it will result in a conflict with our local config.json file upon refreshing the page displaying that resource.
We cshould improve the handler regex in n inmanta-ui for this. However, we made it this liberal so that it works for any view in the SPA. the regex needs to be adjusted, probably with a $ at the end of it.
https://github.com/inmanta/inmanta-ui/blob/97ffa4e69a444b0e85a09a9e07d71fa1eccd0c42/src/inmanta_ui/ui.py#L112
server.add_static_content(r"/console/(.*)config.js", content=config_js_content)