Use single type of unit in columns #8
Labels
No Label
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No Milestone
No project
No Assignees
1 Participants
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: mpana/sc-portal#8
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When listing packages in the creation screen, the disk units switch between GB and TB depending on package's disk size. I think this could potentially cause accidents to anybody not paying attention, so I suggest we stick strictly to a single unit per column (e.g. only GB for the disk column).
The confusion is when creating packages, although this concept should prevail project-wide (i.e. everywhhere). I propose we use GB in all cases and avoid showing things in TB or if we do, than maybe this issue is resolved by the remediation of the sorting issues described in issue #11.