Remove basePath on next page URI to prevent no data available error #1356
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.
GET /topic/{topicName}/data returns in the after variable the URI to call to get the next page of data. When using context-path in Micronaut, the context-path is added in the URI.
![image](https://user-images.githubusercontent.com/2262145/215795920-be59d409-20ee-429d-9efe-f75df6beb5d1.png)
The problem is that we add it another time in the uriTopicData endpoint.
![image](https://user-images.githubusercontent.com/2262145/215795732-2dc46244-8643-4297-b6f0-8914a22a9607.png)
This leads to a /linked/linked/api/... call which fails and show the issue mentionned in #1298.
![image](https://user-images.githubusercontent.com/2262145/215796140-3b6fda14-c687-4b29-baa4-7a630d760899.png)
If we keep only the after URI as it is and don't add the basePath, pagination works well with context-path