fix: use url-safe key and valid base path when rendering apps as web modules #20074
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prior to this change, custom apps were rendered as WebModules in the
/api/apps/menu
API (introduced with the removal or struts) with unsanitized name fields. This causes issues when app names have special characters or spaces. Additionally, the "namespace" property renders the relative base path for bundled apps but incorrectly was set to the name for installed apps.I added also a
basePath
property to theApp
class which exposes the relative base path also under the/api/apps
endpoint.Before this change (including also a bundled app for reference):
After this change:
Note that the relative paths for bundled apps and the lack of case standardization are a bit odd and should probably be improved, but I left those as they were previously for now.