Replies: 1 comment 1 reply
|
Before the 1.0 rewrite, most of the bugs reported were related to JavaScript, so I’m doing my best to keep things static to reduce maintenance. This change is definitely doable, but I don’t currently have the time to implement it myself. If anyone familiar with frontend work is interested in taking this on, I’m happy to assist. I can edit the backend routes to return JSON instead of a flash notification and rendered template. Then all you need to do Is replace classic HTML form with listeners to send requests and display results in If someone is willing to work on this, please let me know and I’ll convert it into an issue. 👍🏻 |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Enabling and Disabling containers should be an AJAX call to the backend, without the page refresh at the end.
It should also show some kind of spinner/loading to inform the user the action is running.
This will provide a much cleaner UI/UX without having to wait for the page refresh for every container we need to start.
If it's to hard to map each row/container for updating the values (usage and enable button color change etc), should at least request a new template from AJAX for the whole section, and replace it, without having to refresh the whole page
NOTE: This should be applied for every "on/off", as for example, the features.
All reactions