[MGNLREST-204] Publish openAPI specs for delivery endpoints Created: 17/Jul/19 Updated: 25/Mar/22 |
|
| Status: | Accepted |
| Project: | Magnolia REST Framework |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Neutral |
| Reporter: | Mikaël Geljić | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 1 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Template: |
|
||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||
| Release notes required: |
Yes
|
||||||||||||
| Documentation update required: |
Yes
|
||||||||||||
| Date of First Response: | |||||||||||||
| Epic Link: | Headless Backlog | ||||||||||||
| Description |
|
Publishing openAPI specs dynamically, based on delivery endpoint configurations is a missing piece (without adding anything to our stack, since we use swagger already for the other endpoints). Worth checking if we can decouple OpenAPI/Swagger support from the `RestDispatcherServlet`;
|