Description
A customer reported that after adding a few alias records, they wanted to list them back for confirmation and didn't see them in the record list. Here's an extract from the Groove ticket:
One piece of feedback: when I tried listing my records with
dnsimple records list example.com
....
My ALIAS record (and many others) was missing, and it wasn't clear to me why. Only after reading all the options the help page for the records list command did I notice it is paginated.
The experience here was not great; here are a couple of suggestions:
- If it's not too hard on the DB, I suggest showing more records by default (maybe 100) as that would be enough for most users.
- For discoverability, it would be best to output a line such as "Showing 25 records (page 1)". While it might be annoying for scripts, the main use case to optimize for is a user in a terminal. You can eventually use stderr for that or disable this warning when piped (no tty).
- And at the very least, in the "help" pages, It would be good to show it somewhere here:
Because we're more likely to go from there (that's what I did) to "dnsimple records list" to "dnsimple records list example.com". And none of those steps mention that.
(of course if you do that, you should do it on all other paginated endpoints ^^)
Expected Behavior or Outcome
- Pagination is more obvious to humans and agents.
Acceptance Criteria
Resources/References
Notes
None
Description
A customer reported that after adding a few alias records, they wanted to list them back for confirmation and didn't see them in the record list. Here's an extract from the Groove ticket:
Expected Behavior or Outcome
Acceptance Criteria
Resources/References
Notes
None