Better formatting of the backups table

uselagoon / lagoon-ui

Apache License 2.0

6 stars 2 forks source link

Better formatting of the backups table #210

Open seanhamlin opened 6 months ago

seanhamlin commented 6 months ago

At present, I see a couple of UX issues with the backup table.

Backup ID - this data is only ever useful for commands that involve restic really, the average user does not care about the backup ID. I think this could perhaps be hidden by default, and available somehow to retrieve for advanced users (e.g. title text, or a copy button or something). This forces the table to squish, e.g. the source column needs more space.
Backup size - this at present is formatted as 680.06MB, I think it could be just without the 2 decimal places, that level of accuracy is not needed.

shreddedbacon commented 5 months ago

Agreed on the backup id. I wouldn't hide it though, but perhaps truncate it, or something similarly to how we can expand and contract the deploy key

Instead of having it display like a secret though, it could just be truncated so it would appear like b80693be... and then clicking the eye would expand it so it could be copied out

tnelson-doghouse commented 3 months ago

I'd also like to see a search filtering box, so that we could eg. just look at the mariadb ones, or just the nginx ones (like the project search box on the projects page). Does that belong here, or should it be a separate issue? Date-based filtering would be cool, but I imagine it'd be more work.
Regarding the decimal points, accuracy isn't the problem in that instance, but if we're looking at eg. 1.1GB vs. 1.8GB, or 1.1TB vs. 1.8TB, then it could make a difference. Not sure if it does that, but thought it a point worth considering before removing it.

HTH,