|
|
|
|
@@ -44,10 +44,27 @@ todo: hide swagger logo and branding in api explorer
|
|
|
|
|
todo: Email notification sb link to edit subscription?
|
|
|
|
|
Might be handy to directly click and turn off a subscription from teh notification?
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
todo: v7 items .net final version update to if possible and feature request for search client notes direct open plus whatever is on the list
|
|
|
|
|
|
|
|
|
|
### MEDIUM ITEMS #######
|
|
|
|
|
|
|
|
|
|
TODO: NEW CLIENT UPDATE ISSUES
|
|
|
|
|
NOTE: This might all be due to package.json needing to have it's version updated
|
|
|
|
|
it might be pulling that into the serviceworker for pwa or consulting it
|
|
|
|
|
NOPE, doesn't make any difference setting package.json version
|
|
|
|
|
|
|
|
|
|
Right now it doesn't always refresh, have to manually do so, it should reload and ditch the cache on update, not sure why it isn't to be honest
|
|
|
|
|
Try a test of it here locally and with release build, check network traffic, is it in fact actually updating and it's just the login page that isn't or...?
|
|
|
|
|
|
|
|
|
|
have an url that opens automatically or a notification and link to one after a new version has been detected just
|
|
|
|
|
like visual studio does in order to show what is new in this version
|
|
|
|
|
maybe ideally it opens to a new document page "whats new in version x.xx"
|
|
|
|
|
this way no need to go beyond the local server or hit our site unnecessarily
|
|
|
|
|
|
|
|
|
|
todo: Client is *NOT* automatically updating no matter what version numbers are set
|
|
|
|
|
Need to look into this and fix it for certain as it will be a huge issue when beta / release generally
|
|
|
|
|
Find the notes already about this, maybe there is a link about serviceworkers etc
|
|
|
|
|
|
|
|
|
|
todo: chunk-vendors has fa-brands in it which is fucking huge, what else is in there I don't need?
|
|
|
|
|
eradicate fa-brands!
|
|
|
|
|
Looks like I'm doing it wrong, I was using a generic NPM module when there is a Vue specific one that also has guidance to limit to just the icons I actually use:
|
|
|
|
|
@@ -66,23 +83,6 @@ todo: chunk-vendors has fa-brands in it which is fucking huge, what else is in t
|
|
|
|
|
Plan: figure out if can ditch it as a dependency and if not then figure out how to work with it now as it's all different
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
TODO: NEW CLIENT UPDATE ISSUES
|
|
|
|
|
NOTE: This might all be due to package.json needing to have it's version updated
|
|
|
|
|
it might be pulling that into the serviceworker for pwa or consulting it
|
|
|
|
|
NOPE, doesn't make any difference setting package.json version
|
|
|
|
|
|
|
|
|
|
Right now it doesn't always refresh, have to manually do so, it should reload and ditch the cache on update, not sure why it isn't to be honest
|
|
|
|
|
Try a test of it here locally and with release build, check network traffic, is it in fact actually updating and it's just the login page that isn't or...?
|
|
|
|
|
|
|
|
|
|
have an url that opens automatically or a notification and link to one after a new version has been detected just
|
|
|
|
|
like visual studio does in order to show what is new in this version
|
|
|
|
|
maybe ideally it opens to a new document page "whats new in version x.xx"
|
|
|
|
|
this way no need to go beyond the local server or hit our site unnecessarily
|
|
|
|
|
|
|
|
|
|
todo: Client is *NOT* automatically updating no matter what version numbers are set
|
|
|
|
|
Need to look into this and fix it for certain as it will be a huge issue when beta / release generally
|
|
|
|
|
Find the notes already about this, maybe there is a link about serviceworkers etc
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
### BIG ITEMS ###
|
|
|
|
|
@@ -101,7 +101,10 @@ todo: DASHBOARD
|
|
|
|
|
- these cases:
|
|
|
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2024
|
|
|
|
|
https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1974
|
|
|
|
|
- Printable, need to test render these same metrics graphs in reports
|
|
|
|
|
- REPORTING / Printable, need to test render these same metrics graphs in reports
|
|
|
|
|
Need to confirm this as I go along, probably need to replicate the graphs at the server end...shit
|
|
|
|
|
could be images also but need to render somewhere
|
|
|
|
|
I guess a wrapper over the graphs so they can be called directly during server render as well as from vuetify at client
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|