You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not every controller of the API changes on every version bump, so we may need to make the same controller available under multiple paths.
Here evaluate different path multiplexing approaches (custom interceptor vs simply duplicating the controller classes) with special attention to the following aspects:
will both (old and new) controllers be represented in the generated openapi document?
how easy/straight-forward is it to introduce a new major version of the API?
how easy/straight-forward is it to remove a deprecated version of the API?
The text was updated successfully, but these errors were encountered:
paullatzelsperger
changed the title
spike: evaluate different path multiplexing approaches (custom interceptor vs simply duplicating the controller classes)
[Spike] Management API: investigate path multiplexing mechanisms
May 15, 2024
Not every controller of the API changes on every version bump, so we may need to make the same controller available under multiple paths.
Here evaluate different path multiplexing approaches (custom interceptor vs simply duplicating the controller classes) with special attention to the following aspects:
The text was updated successfully, but these errors were encountered: