diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index ddf475ae..8219efd7 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -7,9 +7,9 @@ Success is the ability to go from failure to failure without loss of enthusiasm ************************************************************************************************************************************************************************** CURRENT ROADMAP -1) Get the widget edit form completely working with the exception of reporting which can be stubbed out but should be present even if not functional now - - nothing left to determine, ready to copy to other objects and automated testing +1) Get the widget edit form completely working with the exception of reporting which can be stubbed out but should be present even if not functional now - Test manually with all devices before baking it in + - Make automated test for it 2) Get the Widget list and filter and any other options (except reporting) fully working and ready to roll out. - Nothing left to determine, all done, ready to copy and automated test, with a stubbed out reporting UI @@ -46,27 +46,10 @@ CURRENT TODOs =-=-=-=-=-=-= SHELL / NAV / MENUS / LAYOUT - - TODO: WHEN GET TO HERE, POST TO SERVER AND TEST DRIVE AGAIN WITH ALL BROWSERS / DEVICES TODO: Enforce role rights for menu items once it's stubbed out -TODO: maybe some code to check if the server is available and or provide an actual message, right now if click login with server down it appears that nothing happens instead of an error - -TODO: Two kinds of mass fetch records in RAVEN - - 1) Reporting records - - Need to filter, sort and will probably pull in many different tables so would be a set of dedicated objects for that purpose at server - - Not using name display format as it's a reporting responsibility how the raw data is displayed at that point - - 2) Selection records - - USED IN - - In forms in pick lists for selection - - In main grids also for selection and viewing and triggering reporting (but reporting uses different lists to feed to report generator) - - Need to filter sort and search - - Uses templated name display format - - Server needs to take into account display format - - ACTION required: - - Make sure the server supports this TODO: Errors - make sure all user displayed errors have an error number if they might be something tech support needs to know (case 1854) - I guess this is a LT feature really @@ -152,7 +135,20 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM - - Needs to remember last settings (stored centrally) like filter used, number of rows etc - When user opens up AyaNova it should always look the same in each area as last time they were there - + - Some stuff that might not be relevant from earlier (duplicated at server todo project) + - TODO: Two kinds of mass fetch records in RAVEN + - 1) Reporting records + - Need to filter, sort and will probably pull in many different tables so would be a set of dedicated objects for that purpose at server + - Not using name display format as it's a reporting responsibility how the raw data is displayed at that point + - 2) Selection records + - USED IN + - In forms in pick lists for selection + - In main grids also for selection and viewing and triggering reporting (but reporting uses different lists to feed to report generator) + - Need to filter sort and search + - Uses templated name display format + - Server needs to take into account display format + - ACTION required: + - Make sure the server supports this TODO: Make errorBoxError message box on all forms a component instead as it's just boilerplate @@ -220,10 +216,17 @@ TODO: ATTACHMENTS RETEST HERE ON ALL DEVICES +TODO: AUTOMATIC TEST *** SUPER IMPORTANT ***** + - Once widget form is solid then need an automatic UI test for it to get that ball rolling and to ensure no slips during development + - Ideally it will test every input component and validate the entire record round trips properly, maybe it needs to also try different states like creating new, editing etc + - Also function as a "smoke" test that will heavily exercise the server and client repeatedly for as long as I let it run which will reveal issues before releases + +TODO: Locale page with locale settings TODO: Trial route ui support in client (ON HOLD NEEDS BACKEND WORK) - Went to do this but found it's a bit of a maze and has some hacked temp code in the license fetch route etc for development purposes - Need to determine what the actual solution is for production and make some changes at the backend first + - Also this might be the point to start looking at RockFish changes as well - Add an area to support refreshing the database and generating test data - Would be useful to see and manage OPS things related to deployment to server just to save time, can refine them later @@ -282,10 +285,7 @@ TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other form - formstate shit is also menu shit really so can they be combined somehow, like present two sets of menu options one read only and one fully read-write? - some forms will have special needs but could handle them outside of the regular boilerplate shit? -TODO: AUTOMATIC TEST *** SUPER IMPORTANT ***** - - Once widget form is solid then need an automatic UI test for it to get that ball rolling and to ensure no slips during development - - Ideally it will test every input component and validate the entire record round trips properly, maybe it needs to also try different states like creating new, editing etc - - Also function as a "smoke" test that will heavily exercise the server and client repeatedly for as long as I let it run which will reveal issues before releases + TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround