feat: Add 'listAllMappings' action for comprehensive route inspection #367
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.
Description
This PR introduces a new internal action
listAllMappingsto the API Gateway service. This action provides a complete list of all available API endpoints, aggregating both explicitly defined aliases and automatically generated routes (frommappingPolicy: 'all').Why
Currently, it's difficult to get a full picture of all exposed endpoints, especially when using a mix of aliases and auto-mapped routes. This new action helps developers debug their API surface and can be used as a data source for generating API documentation or service discovery tools.
Features
mappingPolicy: 'all'.$with configured special char).Example Usage
call api.listAllMappings { grouping: true }