-
Notifications
You must be signed in to change notification settings - Fork 686
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
Trigger Characters missing in formatAfterKeyStroke #1906
Conversation
omnisharp-roslyn side : OmniSharp/omnisharp-roslyn#1042 |
@TheRealPiotrP: Should there be a label for cross-cutting changes like these that depend on a new OmniSharp build? |
Should this be merged now? |
This is blocked on : OmniSharp/omnisharp-roslyn#1042 and microsoft/vscode#40235 |
@akshita31 still blocked? |
Is there anything blocking this? |
@DustinCampbell I haven't looked into this one for some time. Will take it up now. |
I am not sure what is the correct approach to deal with this. |
Any updates on when this will be merged? |
Any news on this? |
Any Updates on this? It shows it's been waiting to be merged for a while now. |
To take this PR we would need an updated O# change to support opening brace and new line as triggers. Going to close this until there is a change on the O# side. |
Issue : #1591
To ensure proper bracket styling, entering '{' should trigger a format request. Also '\n' is one of the expected characters for triggering the format request. It was present in omnisharp-roslyn but not present as trigger character on the vscode side.
Please review : @DustinCampbell @TheRealPiotrP @rchande