ayanova/devdocs/todo.txt

@@ -4,36 +4,14 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
 =-=-=-=-
 
 
-todo: release and find bottlenecks 2G regular test WITH A POSTED RELEASE
-	set network speed in dev console of firefox to regular 2g then go through all forms and confirm all still works as this will expose any await issues
-	RESULT:
-		2g standard is absolutely fine with the sole exception 
-		it takes forever to initially cache everything and it seems to cache *everything*, not just the pages I visit
 
-todo: enable compression at server nginx
-	https://docs.nginx.com/nginx/admin-guide/web-server/compression/
-
-todo: can I show a "CACHING"..loading indicator on initial hit to the server when it's loading?
-todo: can the "chunk-vendors..." resource be shrunk at all?
-	it's 1mb and then a second one at 549kb and seems to contain VUE and other libs
-		or maybe it can be broken out more so it loads in chunks?
-	https://webpack.jakoblind.no/optimize/
-	https://medium.com/hackernoon/the-100-correct-way-to-split-your-chunks-with-webpack-f8a9df5b7758
-	https://stackoverflow.com/questions/48985780/webpack-4-create-vendor-chunk
-
-todo: THIS!  At this point, upload to dev server and thoroughly test with devices, it seems a bit slow at times
-	- Might need to hide attachments until user clicks on something to reveal as it seems odd to fetch every open
-todo: careful and thorough PERF tests remotely and local
-	- https://www.digitalocean.com/community/tutorials/how-to-use-chrome-dev-tools-to-find-performance-bottlenecks?utm_source=DigitalOcean_Newsletter
-	- https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/reference#rendering
 
 
 todo: ay-evaluate page is triggering a request to the server for Request URL:https://test.helloayanova.com/ay-evaluate
 	server is returning "AyaNova doesn't work without JavaScript enabled. Please enable it to continue."
 	Not sure why
 
-todo: chunk-vendors is 12mb! WTF very much slowing down all other ops
-	Not release mode though
+
 todo: I don't really need About on every edit form, keep it for the main top level and remove it from all the edit forms
 
 todo: concurrency violation tests, so far I don't think I've *ever* tested that from the client itself