VS Code: avoid overaggressive parenthesis removal (in Scala / Metals)

By -

I don't think this is a Scala- or Metals-specific issue, but that's where I'm seeing it.

VS Code aggressively removes parentheses, but not in a symmetric fashion. For instance, if I type the following:

Before image, two sets of parentheses

and I want to remove the inside parentheses, I would start by removing the inner closing parenthesis:

closing inner parenthesis removed

OK, the highlighting is already suggesting the problem: when I removed the inner parenthesis, it is the outer one that looks unmatched.

If I now go ahead and remove the inner opening parenthesis, both the opening and closing parentheses are lost:

mismatched with only opening outer parenthesis remaining

So maybe there is a right way to remove them that I am missing. Instead of removing the inside closing parenthesis, I will start by removing the inside opening parenthesis:

enter image description here

Unfortunately, in this case only the inner opening parenthesis is removed, so it is still mismatched.

Ugly Workaround

So for now, I either remove the inner closing parenthesis, then the inner opening parenthesis (which removes both, as shown), then I go back and add the lost closing parenthesis). Or, I remove the inner opening parenthesis, then go to the end of the line and remove that extra closing parenthesis.

Because I'll do this hundreds of times a day, the few wasted keystrokes really add up.

What did VS Code want us to do here? What is the right way to engage with its parenthesis autodeletion?



Comments

Post a Comment

Popular posts from this blog

Today Walkin 14th-Sept

By -
Image
14th Sept 2017 ( GO Through all List) Read Walkin details properly , Try to call company before attending if possible !!! ==================================== 1. Myntra through fresherworld (Call Based , Venue shared to shortlisted candidates) _____________________________ 2. Magna : Hiring for Client Harman : C++
Read more

Hibernate Search - Elasticsearch with JSON manipulation

By -
Elasticsearch with JSON manipulation Elasticsearch ships with many features. It is possible that at some point, one feature you need will not be exposed by the Search DSL. To work around such limitations, Hibernate Search provides ways to: Transform the HTTP request sent to Elasticsearch for search queries. Read the raw JSON of the HTTP response received from Elasticsearch for search queries. Direct changes to the HTTP request may conflict with Hibernate Search features and be supported differently by different versions of Elasticsearch. Similarly, the content of the HTTP response may change depending on the version of Elasticsearch, depending on which Hibernate Search features are used, and even depending on how Hibernate Search features are implemented. Thus, features relying on direct access to HTTP requests or responses cannot be guaranteed to continue to work when upgrading Hibernate Search, even for micro upgrades (x.y.z to x.y.(z+1)). Use this at your own risk.
Read more

Spring Elasticsearch Operations

By -
Elasticsearch Operations Spring Data Elasticsearch uses two interfaces to define the operations that can be called against an Elasticsearch index. These are ElasticsearchOperations and ReactiveElasticsearchOperations. Whereas the first is used with the classic synchronous implementations, the second one uses reactive infrastructure. The default implementations of the interfaces offer: Read/Write mapping support for domain types. A rich query and criteria api. Resource management and Exception translation. ElasticsearchTemplate The ElasticsearchTemplate is an implementation of the ElasticsearchOperations interface using the Transport Client. @Configuration public class TransportClientConfig extends ElasticsearchConfigurationSupport {   @Bean   public Client elasticsearchClient() throws UnknownHostException {                      Settings settings = Settings.builder().put("cluster.name", "elasticsearch").build();     TransportClient client = new P
Read more