This commit is contained in:
2018-08-23 18:57:14 +00:00
parent cad59a7aa9
commit eeb0b1496c
4 changed files with 63 additions and 36 deletions

View File

@@ -8,32 +8,21 @@ Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTI4MjEyNjI5IiwiZXhwIjoi
CHOPPY DAY WORK
+++++++++++++++
https://severalnines.com/blog/performance-cheat-sheet-postgresql
https://medium.com/@wesharehoodies/immensely-upgrade-your-development-environment-with-these-visual-studio-code-extensions-9cd790478530
Changes needed to routes??
- http://www.talkingdotnet.com/actionresult-t-asp-net-core-2-1/
CODING WORK
+++++++++++
Need to revise my metrics to bring in mvccore instead of mvc?:
- https://github.com/AppMetrics/AppMetrics/issues/261#issuecomment-404051808
Might be time to order all this to the best effectiveness if it isn't already.
Error messages / Numbers
- All server error codes start with E1000, all API error codes start with E2000
- Look for English text in all the messages so far and see if can be localized even crudely by google translate and do so
- Make sure error numbers have a consistent system and don't conflict, I think there are two sets of error numbers, there should only be one
- Make sure Every error has a number and that is documented in the manual
- Locale keys for error numbers?? i.e. E1000, "blah blah error 1000"
Cleanup and sticking to the following code convention:
All names are PascalCaseOnly with the following two exceptions:
- function paramenter names are ALWAYS camelCased
- CONST values are ALL_CAPS with underlines between for spaces
Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
- Audit log
- Localized text
- Search and search text indexing
- Auto visible id number assigning code
Created/Changed/Modifier/ Change / Audit log
- Flesh out and implement fully
@@ -42,13 +31,7 @@ Created/Changed/Modifier/ Change / Audit log
- Tests
- Do I add more fields to the objects to cover same as v7 (currently only created is there in widget and others) or do I make use of the changelog table for that shit??
Changes needed to routes??
- http://www.talkingdotnet.com/actionresult-t-asp-net-core-2-1/
Overall plan for now: anything standing in the way of making the initial client shell UI needs to be done first, everything else can wait
- Localized text
- Search and search text indexing
-
Ensure all modern best practice security is properly enabled on helloayanova.com so testing is valid
- https://en.wikipedia.org/wiki/HTTP_Strict_Transport_Security#Deployment_best_practices