Fixed apiexplorer
This commit is contained in:
@@ -17,7 +17,12 @@ Need to consider re-thinking versioning system of api to remove the complexity o
|
||||
Test out versioning in the test project I made following the Swashbuckle guide for multiple docs:
|
||||
https://github.com/domaindrivendev/Swashbuckle.AspNetCore#list-multiple-swagger-documents
|
||||
|
||||
Because maybe this is the way to go?
|
||||
|
||||
- Update my code to the modern standard: https://kimsereyblog.blogspot.com/2018/08/apicontroller-attribute-in-asp-net-core.html
|
||||
- Note that that above is for v2.2 my controllers appear to date from the v1 .net core era and I will need to then move them to the .netcore 3.1 era changes
|
||||
- This is important and worth doing to make sure everything will work going forward (the swashbuckle [apicontroller] attribute debacle is proof of this)
|
||||
|
||||
|
||||
|
||||
|
||||
Need a sprint to get to a fully testable client with entry form, list and as much as possible all features from COMMON-* specs list
|
||||
|
||||
Reference in New Issue
Block a user