Is your feature request related to a problem? Please describe.
Another suggestion: There is a big JavaScript song-and-dance in the Seed Database IP Device edit form when clicking the "Check connectivity" button. This ultimately retrieves a JSON status response from the backend and spends a lot of cycles putting that response data into the right places of the UI (some as display, some as replaced form elements). This whole thing could be simplified a lot by using HTMX.
Originally posted by @lunkwill42 in #2639
Describe the solution you'd like
The connectivity test is only ever used on this SeedDB page, and there is therefore no benefit to keeping it around as a private REST API.
Clicking the "Check connectivity" button should, instead of kicking off an AJAX request and parse JSON responses, just initiate an HTMX request that swaps in the results of the connectivity tests directly into the DOM.
Additional context
Screenshot of connectivity test results after clicking the button once:
There are also recently added management profile types (like REST API types) that do not have connectivity checks, which causes strange error messages to appear in the current JS-based implementation. These error messages could be improved in lieu of actually implementing connectivity tests for these profiles. See #3275 for details.
Is your feature request related to a problem? Please describe.
Originally posted by @lunkwill42 in #2639
Describe the solution you'd like
The connectivity test is only ever used on this SeedDB page, and there is therefore no benefit to keeping it around as a private REST API.
Clicking the "Check connectivity" button should, instead of kicking off an AJAX request and parse JSON responses, just initiate an HTMX request that swaps in the results of the connectivity tests directly into the DOM.
Additional context
Screenshot of connectivity test results after clicking the button once:
There are also recently added management profile types (like REST API types) that do not have connectivity checks, which causes strange error messages to appear in the current JS-based implementation. These error messages could be improved in lieu of actually implementing connectivity tests for these profiles. See #3275 for details.