How to format the code with keyboard shortcut? - flutter

How can I format the code with keyboard shortcut
I usualy used Ctrl S in dart files
but in some files dont work , and i see youtuber make it easy in keyboard but no one say how.

In Visual Studio Code enable Format On Save setting

Related

Cannot type upper case E in VS Code and Python [duplicate]

I would like to change the keyboard shortcut for quick fix in Visual Studio 2013, so that it matches the ReSharper equivalent (which I only use on my office machine). How can I do it?
One way to do it is to enter on the menu 'Tools', 'Customize' and click on the 'Keyboard...' button near the 'Close' button.
Inside this option you can search for the commands by name (I couldn't find the Quick Fix here), maybe you want the Edit.FormatDocument one, that makes the indentation for the documents automatically.
If you can't find this option, tell me your quick fix actual keyboard shortcut, so I'll be able to check which function it calls.
I did some research on the R# QuickFix option and maybe what you want is this is the option you want: View.ShowSmartTag.
Look at this doc: Identify and customize keyboard shortcuts in Visual Studio

How to get keyboard shortcut `Cmd + S` to save on VS Code?

When I attempt to save my file on Visual Studio Code with the cmd+s keyboard shortcut, it does not save the code. I have to manually click File, the Save, just to be able to save my progress. I'm using macOS Catalina version 10.15.7 and VC Code version 1.55.2.
How do I fix this?
Attempts:
-Checked if ⌘ Cmd + S keyboard shortcut is tied to the Save functionality
If you do it right this solution will fix your issue.
I have never had a problem saving with VS-Code personally, but I have had issues with keybindings. IDK if you write your own keybindings, but if you do, you might want to check the keybindings that you have wrote to make sure they do not conflict with [CTRL + S]. The keybindings.json file that you create custom keybindings in, overrides the default keybindings.json file that defines the keybindings that VS-Code ships with.
To check your keybindings.json file...
Hit the F1-Key
A menu will drop open type in "Keyboard Shortcuts"
There will be two Preferences: Keyboard Shortcuts
Make sure to select Preferences: Keyboard Shortcuts and not Preferences: Default Keyboard Shortcuts
If the file is empty you are good. If you have keybindings written in the file, you need to iterate through them by hand, checking each one. Make sure that none use [CTRL + S] together. Even if the keybinding uses [CTRL + S] and other keys, you will need to disable it, so you can test if it is causing an issue.
Debugging [CTRL + S]
If your keybindings.json file is all good, then great, that's one thing to scratch off the list. The only thing left to do now is debug the Bound Key ("Key Binding"). To debug keybindings, you will use a built in tool, that VS-Code offers. To start do the following:
Hit the F1-Key
When the quick input drops open type the following into the text input:
"Toggle Keyboard Shortcuts Troubleshooting"
Select the option: Developer: Toggle Keyboard Shortcuts Troubleshooting
It should automatically open the OUTPUT panel, which is located in the same panel that your terminal is. Make sure that the OUTPUT is set to LOG(Window) in the drop down. (I took a picture and posted it below if you can't find the Keyboard Shortcut Troubleshooter).
The image might have funny declensions because I am on a dual monitor setup with 1 1080x1920 curved screen and one 1080x720 screen.... I cropped it to a STD HD 1920 width.
I Got My Trouble-shooter working, and Output open, now What Jay?
Okay... Well your at the right spot. Now every-time you press some keys, you should see your OUTPUT WINDOW working like crazy. It should be logging all sorts of stuff, which is good, very good.
This Part Is Important! READ CAREFULLY
What you want to do is use your keybinding that you feel isn't working appropriately. Use it when focus is set on an editor, use it when focus is set on a different editor, use it when focus is set on the sidebar. Where you are focused at in the editor at any given time can greatly affect a keybinding. The output is gonna write lines every-time you use your keybinding. Try not to hit any other keys while doing this, so you have a column in you output that includes logging from the keybinding you are testing only. Read the output see what it says. See if it looks right, or wrong. If it looks wrong, you can visit this link, to the VSCode site that covers this topic, and see if you can fix it your self. If you can't fix it your self, come back here, and edit your question. When you edit your question make sure that it includes the Troubleshooter's Logging Output.
VSCode Troubleshooting Keybindings (Keyboard Shortcuts) # https://code.visualstudio.com/docs/getstarted/keybindings#_troubleshooting-keybindings
Image that shows how to open the Keyboard Debugger
Also shows how to set the OUTPUT to Log(Window)
StackOverflow-2021-JUNE-26018:34-PST
Another thing to check for is, for lack of a better term, combination key bindings. For example, I was having an issue with ⌘+s. VSCode gave a message that it was waiting for the second key binding. After looking at the keybindings.json, I noticed I had a key binding for opening up user snippets as
{
"key": "cmd+s cmd+n",
"command": "workbench.action.openSnippets"
}
The ⌘+s portion of this key binding conflicted with the default ⌘+s

How to search ('Ctrl+F') in 'output' panel in VS Code?

I used to be able to be able to Ctrl+F to search whatever was logged in VS Code. Now, for some unknown reason, the search bar doesn't show up when I type in Ctrl+F.
I am on version 1.57, which is the latest at this time.
This question if for the Debug Console which isn't the tab I am looking at.
Click anywhere inside the output panel, and then press Ctrl + F
I realized that the Vim extension is what is causing this. Ctrl+F is for scrolling and although previously Vim keyboard shortcuts didn't work in the output panel, they seem to have been extended to it recently see this issue I raised.

list arguments in vs code

I am switching from android studio to VScode for flutter development and, obviously, there are some shortcuts that on android studio different from those on VScode. One of those shortcuts that I could not find is the listing of all arguments of a widget. I am looking for a shortcut that lists all the args without entering any letter.
I used cmd + space and nothing happend. I also used shift + cmd + space and gave me something I am not looking for. So can anyone help me with that?
CTRL + space works.
To check your keybinding, go to Preferences > Keyboard Shortcuts, and search for Trigger Suggest.
But also make sure you have the Flutter & Dart extension to get code hint/completion:
Dart: https://marketplace.visualstudio.com/items?itemName=Dart-Code.dart-code.
Flutter: https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
Just CTRL + space works for me. I installed Intellij keymap as an extension on my VSCode too Here is an image of my vscode.
Sugestions without type anything
For a given widget VS Code auto-completion provide both method and class, respectively purple and yellow symbols.
An option is to select the class of the widget you want to use instead of the method in the auto-completion list. Then, as soon as you will add the opening parenthesis, all arguments will be listed and available for selection.

Can Visual Studio Code `quick fix` interact with keyboard?

I am using VS Code with the excellent vscodevim extension. When I navigate to a code that has a Quick Action available I can ctrl + . to activate the drop down context menu.
Is there a way to select toggle through the list of available items using the keyboard - other then the arrows keys. As a point of information, within Visual Studio it is possible using tab, this does not work in VS Code.
Why? 'cause I love my MS ARC keyboard but I hate the rocker arrow keys.
This is a known issue for linux users using vscode with advanced shortcuts like vim extension in your case, for some reason quick fix contextual menu is unattached from vscode shortcuts which makes shortcuts not work. A really easy workaround to use with a graphical interface is HotKey.
HotKey > https://github.com/autokey/autokey for Linux and create your own shortcut.