feat(UI): make small UI Tweaks

[colton-lapp]

This PR makes two small UI tweaks.

Fix display for artifact tasks to remove unused "Input Parameters":

• Remove the "Input Parameters" from the Artifact Plugin Task registration table (you cannot set input parameters for Artifact Plugin Tasks in the UI) while keeping "Input parameters" for Function Plugin Tasks

Enhance UI by adding loading indicators:

• Implement loading animation with minimum 300ms loading for all tables i.e. entrypoints, jobs, artifacts, etc (implemented minimum loading time to remove "flicker" effect. We could implement advanced logic to not show the loading animation for the first 300ms or so instead.

Potential future changes we could work on after discussing with the team:

• Enable multiple selection and deletion in all tables. Checkboxes on each row would allow you to select multiple, and then a button would let you delete all of them.
• "Save parameter and add another" feature - when creating an entrypoint parameter, add a button that says "Save parameter and add another" which would save the current parameter but keep the dialogue box open for additional parameters. Small quality of life improvement to increase speed
• Job log display tweaks - adding color for severity, syntax highlighting potentially, filters, etc to log view for job

[henrychoy]

Not sure what "Thinker" is here?

[henrychoy]

put on separate lines

[henrychoy]

Just a nitpick, but some of the indents on the edits in this file are off

[henrychoy]

Hi Colton,
I think the changes look great. The 300ms minimum loading time for the table looks good.

The multiselect/delete on the plugins page looks good as well, but it clashes with the "click to open" workflow that the rest of the pages follow. think if the team really wants the ability to multiselect, maybe we can add a small "delete multiple" checkbox somewhere in the header of the table. But I think the rest of the team will have some thoughts as to how we want to approach multi-select in general, will probably be a good topic for next call.

[colton-lapp]

Hi Colton, I think the changes look great. The 300ms minimum loading time for the table looks good.

The multiselect/delete on the plugins page looks good as well, but it clashes with the "click to open" workflow that the rest of the pages follow. think if the team really wants the ability to multiselect, maybe we can add a small "delete multiple" checkbox somewhere in the header of the table. But I think the rest of the team will have some thoughts as to how we want to approach multi-select in general, will probably be a good topic for next call.

I agree the team should probably weigh in on the multi-select / delete logic. I could clean up the PR to address your edits and delete the text artifact for loading though. I wonder if there is some way to put the "wait 300 ms" logic into a decorator or standalone wrapper function so that it's not repeated everywhere... maybe eventually we could enhance the logic to not show loading if the request takes less than 100ms. I'm still very new to Vue / Quasar, so I don't really know what the best pattern is here.

[henrychoy]

Hi Colton, I think the changes look great. The 300ms minimum loading time for the table looks good.
The multiselect/delete on the plugins page looks good as well, but it clashes with the "click to open" workflow that the rest of the pages follow. think if the team really wants the ability to multiselect, maybe we can add a small "delete multiple" checkbox somewhere in the header of the table. But I think the rest of the team will have some thoughts as to how we want to approach multi-select in general, will probably be a good topic for next call.

I agree the team should probably weigh in on the multi-select / delete logic. I could clean up the PR to address your edits and delete the text artifact for loading though. I wonder if there is some way to put the "wait 300 ms" logic into a decorator or standalone wrapper function so that it's not repeated everywhere... maybe eventually we could enhance the logic to not show loading if the request takes less than 100ms. I'm still very new to Vue / Quasar, so I don't really know what the best pattern is here.

I think the way you implemented the minimum 300ms loading is the most logical, even if there's some repeated code. One other idea is to implement the minimum loading time in the getData function in the dataApi.ts file... but looks like not all tables use that function (for example the job logs table), and some dropdowns use that function as well. Doing it in TableComponent was my next idea, but I dont see an easy way to implement it there. If we try to respect the separation of concerns, I think the way you did it is probably the best way.

[colton-lapp]

Sounds good! Well I deleted/reverted the code that implemented the "delete multiple" in the PluginsView, which should address all your comments. If it looks good to you, we can merge the loading functionality and the artifact task registration changes into dev