devdocs/todo.txt

@@ -11,20 +11,15 @@ UPDATE all the things before commencing work
 	- https://github.com/domaindrivendev/Swashbuckle.AspNetCore#swashbuckleaspnetcoreannotations
 	- 
 
-Metrics and swagger broken after update.
+- Get tests passing
-Need to consider re-thinking versioning system of api to remove the complexity of swagger bullshit when using versioned api.
+- See about Metrics which is currently commented out in startup, maybe not an issue right now?!
-
+- Read this and see if more areas where I need to update my code to the modern standard: https://kimsereyblog.blogspot.com/2018/08/apicontroller-attribute-in-asp-net-core.html
-Test out versioning in the test project I made following the Swashbuckle guide for multiple docs:
+- Find and read changes for 3.1 dotnet core and 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 
-https://github.com/domaindrivendev/Swashbuckle.AspNetCore#list-multiple-swagger-documents
-
-
-- 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 
 Do the stuff in the Client todo first then back to the server as required.