How to disable auto-format in DataGrip - datagrip

Version
DataGrip 2018.3
When I type ')', it auto-format my sql
Happened after upgraded from version 2018.2
Disable formating is not helping.

That's a bug which is going to be fixed: https://youtrack.jetbrains.com/issue/DBE-7399

Related

Visual Studio added spaces on empty line

a couple of days ago I updated my VS to Microsoft Visual Studio Enterprise 2019 Version 16.8.3 (+resharper 2020.3 version)
And I catch the next case: VS begins to add spaces for an empty line (on the enter keyboard press).
[edit]: This is a ReSharper option. As mentioned by Piers Myers in the comments.
But before it adds spaces only after I write something in a new line:
Maybe somebody resolves this?
This is a ReSharper bug and they are working on it. I will edit this answer when they will release a fix.
[Edit]: The fix will be available in 2020.3.1 version of resharper.
Link to the issue: RSRP-482555

visual studio 13 ssrs expression builder seems disabled

Can anyone tell me why the expression builder seems disabled and how to fix it?
Reinstalling VS seemed to be the only fix.

Aptana Studio 3 indicate lines to be error that aren't

Aptana thinks the below line is an error but the ruby doesn't complain about it!
How to fix it?
Or disable the error indicator in Aptana?
Or update the ruby version that Aptana uses to indicate errors to solve this issue?
Thanks in advance.

Visual Studio 2015 Enterprise with ReSharper 10 Ultimate -- Cannot be properly resolved

I have Visual Studio 2015 Enterprise, version 14.0.24720.00 Update 1 as well as ReSharper 10 Ultimate, version 10.0.2 installed. I have a typescript file that is using AtScript syntax to refer to the Angular2 directive module, as its annotation. However, ReSharper is stating the following error:
Symbol 'Directive' cannot be properly resolved, probably it is located in inaccessible module.
Below is the full error tooltip.
The application compiles and runs as expected, and the angular portions of the application also function as desired. It appears as though this is a ReSharper false negative. Is anyone familiar with a workaround other that simply disabling ReSharper or ignoring the warning?
The issue is simply a bug with the latest version of ReSharper, if you Suspend ReSharper the issue simply goes away and all the source code works as expected.
Update
This has since been addressed in the ReSharper 2016.1 version.
As a workaround, if you are using angular2 from your node_modules folder, then you can reference it directly instead of relying on the new node module resolution. For example you can do:
import {Directive} from '../../node_modules/angular2/core';
As of 02/2016, the issue is fixed in the ReSharper Ultimate 10.1 EAP 3
this version still has some other typescript issues though
Original answer, explaining why it couldn't work in previous versions:
Had the same setup and same issue. I strongly believe this is related to: "moduleResolution": "node"
https://youtrack.jetbrains.com/oauth?state=%2Fissue%2FRSRP-273158
Unfortunately, no way now. We're working on node.js support for the next ReSharper version.
If updating to latest ReSharper version does not work and this only affects .js(x) and .ts(x) files you only need to suspend those. You can do that by going to ReSharper -> Options -> Unclick JavaScript and TypeScript.
It could be Resharper problem. disable it from tools->option->Resharper Ultimate->General->Suspend Now and the errors will be hide.
I was getting the same problem on one of my modules on Resharper 2017.1 in Visual Studio 2017.
But after updating my Resharper to 2017.2.2, that solved the problem.

Can Resharper be turned off for a while?

I'm pairing with someone who is against using resharper (don't ask me why) so I'd like it to hide without uninstalling - is this possible?
For R# 5.0: Tools->Options->ReSharper->Suspend
older versions can be disabled from Add-In Manager menu

Resources