Describe command could use an auto refresh option
See original GitHub issueGreat work on the new updates, it’s been a huge productivity win!
I really like the new describe how it outputs to the editor window vs the terminal.
When I’m troubleshooting container start ups, I find myself re-clicking describe over and over. It would be great if there was a capability to auto refresh describe on a specified interval (it would stop once the editor window was closed by the user)
Could be accomplished either by:
- User config (
describeAutoRefresh &
describeAutoRefreshInterval`) - Separate context menu (Describe - auto refresh)
Issue Analytics
- State:
- Created 5 years ago
- Comments:6 (1 by maintainers)
Top Results From Across the Web
describe-instance-refreshes - AWS Documentation
Description. Gets information about the instance refreshes for the specified Auto Scaling group. This operation is part of the instance refresh feature in ......
Read more >How to Auto Refresh in Google Chrome Browser - YouTube
In this tutorial, I show you how to auto refresh tabs and websites in Google Chrome. This means you can aut...
Read more >VS Code Live Server – How to Auto-Refresh Your Browser ...
In this post, I will explain the details of how it works and how to set up and configure a live server in...
Read more >Refresh an external data connection in Excel - Microsoft Support
Refresh key and command summary ; Check refresh status. Double-click the message, "Retrieving Data" on the status bar. Message box: Retrieving Data ;...
Read more >7 Refreshing Materialized Views - Oracle Help Center
A materialized view can be refreshed automatically using the ON COMMIT ... You can define a default option during the creation of the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hmm, this one might take some pondering. I worry about using global config for things where I think users will often really want the behaviour to depend on context, but I take your point about configuring the default. And thinking further about it, I’m not sure we want the clutter of a toolbar-style UI just for a Describe which should have more of an editor window feel.
Yeah, I think briefly highlighting stuff that has changed is more sensible than a diff view. I just wanted to avoid having to do any work. grin
Now I have bizarre fantasies of an ‘auto diff’ view where every time it auto refreshes it shows you the diff from the previous description. SEND HELP