Feature request: Version Manager for JavaScript and CSS

[Light-Wizzard]

Currently all versions of JavaScript and CSS are Hard Coded; causing the developers to have to edit the templates to update them; this can be corrected by creating a class that tracks what version level every library is at; and this can be a config file or a database call at run time; it would allow you to update either without having to change existing templates. You could add the field names to the template itself as a variable, and only call the function once at run time to fill the values.

Upgrading from bootstrap 3 to 4 will require template changes; and you know this needs to be done; and this will make that transition easier; and do it all at once; if you need compatibility with ver 3; you can just use to different templates; it complicates things; but makes the transition easier for end users; so I would recommend upgrading to 4 at the same time.

if you can decide on what method you would like to see this done; I will work on this also and do a pull request; the truth is that these are all the changes I have to make to use it; so I have to do the work if you do not have the time; I am Medically Retired; so I have the time; and the need for all my Feature Request; so I make them more to open up a discussion on how to implement it then anything else.

Also I will send you a URL so you can see these changes in action and running before you look at the code I push; so you know it is working and how it works; you will want to test it out yourself, and make sure I use the best practices, and do not cause any errors in the app; Quality Control stuff.

Update: Upgrading to Bootstrap 4 means JavaScript updates also; one way to get around versions; and simplifying version control is to use SAS tools, and Node Magic to compile them at start up; that way your resource file name never changes; and there is no reason to track the version; a much better approach; but it requires the use of Nodes; and other tools that the go lang community use everyday; so it was an after thought; another way of doing the same thing; you could also just rename the updated files without using the version number; but then you could not use a CDN; so the above solution is better for that; but if you host your own JavaScript and CSS files; you could use this approach; so I will leave you with two approaches to the same Problem; and that what scripts and css do you need for Bootstrap 4; because Popper comes to mind; plus updated jquery and adding jquery-slim to the mix; with this method you can combine all your JavaScript and CSS into one file and Minimize it; even Optimize the JavaScript on the fly with a rebuild of all the script if any of them change; so this approach has its advantages; but it will also make the startup time slower if it has to generate them at startup; so you could just make rebuilding a button in the app; it does not require a reboot; so its easy to do; and only gets done when its needed; and does not require Nodes to Monitor for Files Changes; or what ever program you use that monitors files changes in real time and triggers this event; sending an encode request to the command line; or a manual button to keep it simple; even with CSRF checks having links like this can be dangerous if ran in a loop; even using slots; you would have to include a meter; and only allow so many calls per hour; and only one call per minute; so you can minimize the risk; just do not forget about it; or find a better way to do this; which safer might be to check for updates at startup; or require a database change that is checked at a preset time in the code; and used to do such background checks; so a watchdog function; keep in mind these are just files that get read every time and are cached in the users cache; so you have to reset the cache date on the file or it will never get updated in the client browser; so the template files are not static; they still require a version control system; that out dates the cache date; thus triggering a client side update.

Thanks