You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The shortcut to jump to a resource's owner is only available in the list view (implemented in #2700)
It is not obvious that this feature is available when inspecting the resource (via Describe or YAML views)
While looking to create a feature request, I checked existing issues and found #2696 (dupe of #1747) which pointed to completed PR #2700 which had the source code for the short cut Shift-J.
Describe the solution you'd like
It would be good if the same shortcut Shift-J was also available in the resource's Describe and YAML views (and any other diagnostic views at the individual resource level).
Describe alternatives you've considered
Use Escape out of the existing Describe or YAML views to go to the list view and then use existing Shift-J shortcut.
Additional context
Shortcut found in pod list view:
But not found in pod's describe view:
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem?
The shortcut to jump to a resource's owner is only available in the list view (implemented in #2700)
It is not obvious that this feature is available when inspecting the resource (via
Describe
orYAML
views)While looking to create a feature request, I checked existing issues and found #2696 (dupe of #1747) which pointed to completed PR #2700 which had the source code for the short cut
Shift-J
.Describe the solution you'd like
It would be good if the same shortcut
Shift-J
was also available in the resource'sDescribe
andYAML
views (and any other diagnostic views at the individual resource level).Describe alternatives you've considered
Use
Escape
out of the existingDescribe
orYAML
views to go to the list view and then use existingShift-J
shortcut.Additional context
Shortcut found in
pod
list view:But not found in
pod
'sdescribe
view:The text was updated successfully, but these errors were encountered: