-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: allow configuring default sort columns for each supported resource #795
Conversation
This is how the table that shows different options when using
Is this too much? Or should we keep all the entries fort |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #795 +/- ##
==========================================
- Coverage 59.60% 59.47% -0.14%
==========================================
Files 210 210
Lines 7655 7667 +12
==========================================
- Hits 4563 4560 -3
- Misses 2450 2458 +8
- Partials 642 649 +7 ☔ View full report in Codecov by Sentry. |
EDIT: Scratch that. |
I'd rather keep it explicit, unless we have a clear list of resource names.
Could we keep the |
We could either:
It's a style question, I don't like mixing dots and dashes for the key, but I think it would be best for consistency and readability if we did. Edit: I just noticed that the environment variables contain dots. That's a bug/oversight. I don't think env vars support dots in their names. |
Nope, env vars cannot have dots:
https://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap08.html |
Without taking a look at the code:
|
adafb8c
to
513372e
Compare
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
While testing this, I found that
Thinking it would end us as
So feature works technically, but the UX was unexpected |
Even with |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I noticed that this PR does not compile anymore because of #798. Could you rebase this PR and fix the compilation error?
The functionality works great now!
9b23dfc
to
23ce28c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🚀
🤖 I have created a release *beep* *boop* --- ## [1.45.0](v1.44.2...v1.45.0) (2024-07-17) ### Features * allow configuring default sort columns for each supported resource ([#795](#795)) ([f6877a1](f6877a1)) * better error messages on malformed option value ([#798](#798)) ([8c6fec9](8c6fec9)) ### Bug Fixes * **config:** ordering of list option values not preserved ([#805](#805)) ([1ac27bf](1ac27bf)) * debug log is truncated if it already exists ([#793](#793)) ([c3d3a9f](c3d3a9f)) * **firewall:** wrong wording when firewall is removed from resource ([#812](#812)) ([9017a65](9017a65)), closes [#809](#809) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
This PR adds options to configure the default sorting column for each resource that supports the
list
command.See #418 and #434