Skip to content

Replace resource number spinners with preset dropdowns in container Resources#419

Draft
horner with Copilot wants to merge 3 commits into
mainfrom
copilot/improve-storage-inputs
Draft

Replace resource number spinners with preset dropdowns in container Resources#419
horner with Copilot wants to merge 3 commits into
mainfrom
copilot/improve-storage-inputs

Conversation

Copilot AI commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

The RAM/Swap/Storage editors used a raw number input whose up/down arrows nudged megabyte values by a single step, making it tedious to reach useful sizes like 4096 MB.

Changes

  • New ResourceValueInput component — a preset dropdown of common sizes with a Custom… option that reveals a number input for precise editing. MB presets that divide evenly render as whole GB (e.g. 40964 GB).
  • ResourcesSection wiring — added per-resource presets and bumped the custom-edit step to multiples of 1024 (RAM/Swap) and 10 (RootFS); swapped the inline number input for ResourceValueInput.

Presets: RAM 256 MB–32 GB, Swap 0 MB–16 GB, CPUs 1–32, RootFS 5–500 GB.

<ResourceValueInput
  label={opt.label}
  unit={opt.unit}
  min={opt.min}
  step={opt.step}
  presets={opt.presets}
  value={editValue}
  onChange={setEditValue}
/>

The editable number field is retained via Custom…, so arbitrary values are still supported. Both the dropdown and input carry ARIA labels.

Copilot AI changed the title [WIP] Fix storage inputs in the Resources for better user experience Replace resource number spinners with preset dropdowns in container Resources Jul 17, 2026
Copilot AI requested a review from horner July 17, 2026 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Storage Inputs in the Resources are not helpful for most users

2 participants