API endpoint for extensions and modules #330
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
currently forms and downloads module use the "legacy" module-endpoint. |
|
At least the /module endpoint should not be deprecated because it is used to provide ja and css files from modules. These cases should not be in the /API endpoint. |
|
I think, the api should be an experimental featurea at first and deactivated by default. Activation should be possible per site. |
added 3 commits
November 20, 2024 16:38
endpoint for navigation tree deactivate api by default and make it activatable for site
add links to content and frontend
|
For security reasons content and navigation endpoints should not be public |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR introduces a /api endpoint for extensions and modules.
The old endpoints will be deprecated.