Repository navigation
Add droplet size descriptions and filtering across interactive commands - #84
Conversation
- Add a Type column from DigitalOcean's own `description` field, so tier names come from the API - Prompts accept a filter: `cpu>=8 mem>=32 price<=300`. - Prompts get readline line editing and up-arrow history.
ret2libc
left a comment
There was a problem hiding this comment.
Please use one consistent default unit for memory filters—GB would work—and document it in the prompt help. Currently, mem>=1023 means 1023 GB, while mem>=1024 means 1 GB. Explicit mb/gb/tb suffixes can remain supported.
Filtering should be available wherever users select a droplet size, including interactive creation, initialization, and both resize paths. The shared helper appears to cover these already; please add command-level tests for interactive creation and resizing to verify that integration, and broaden the PR title to reflect the scope.
ret2libc
left a comment
There was a problem hiding this comment.
Reviewed the current head. The size filtering behavior and command integrations are covered; 384 tests pass with color enabled. The ANSI assertion in one test fails only under this workspace’s NO_COLOR=1 setting.
descriptionfield, so tier names come from the API and are described vs only a slug name such asso-2vcpu-16gb-intelcpu>=8 mem>=32 price<=300.The following image shows the result of running

? mem >= 16 price <= 200, together with the accompanying machine descriptions