-
Notifications
You must be signed in to change notification settings - Fork 0
Change request mapping to '/pid/' for PidRedirectController #30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -31,7 +31,7 @@ | |
| import java.util.*; | ||
|
|
||
| @Controller | ||
| @RequestMapping("/") | ||
| @RequestMapping("/pid/") | ||
|
||
| @Log | ||
| public class PidRedirectController { | ||
|
|
||
|
|
@@ -163,4 +163,4 @@ private Optional<String> determineRedirectPathBase(String entityPid, List<String | |
| .map(entity -> Ascii.toLowerCase(entity.getClass().getSimpleName()) + "s") // Determine path base | ||
| .findFirst(); // Take the first one that matches | ||
| } | ||
| } | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change modifies the base path from
"/"to"/pid/", which is a breaking API change. The endpoint that was previously accessible at/{pidValue}will now be accessible at/pid/{pidValue}.This will break existing clients that are using the old endpoint. Consider:
Alternatively, if the old
"/"mapping was too broad and conflicted with other routes, consider if this is the intended behavior.