This used to work before.
I keep the sql stored procedures source code in sql files on disk. They are the source of truth for the sql objects code, not the objects in the various databases.
Before, if I clicked on a column of a view referenced in a stored procedure edited as a sql file, DG used to take me to the sql file containing the source code of the view on disk, not to the source code of the sql object found in the database.
How far was that in the past? I don't know. I don't use DG all the time, but I recall I was very happy because DG opened the file instead of database objects. Right now, it is very annoying because in Database Explore I have 3 servers, each from a different environment. Please note that I added the folders containing the sql objects source files in the Files window via Attach Directory to Project.
Did you guys make any changes recently? Is there an option where I can force DG to look on disk instead of the database?
Build #DB-232.9559.28, built on August 16, 2023
Runtime version: 17.0.8+7-b1000.8 amd64
VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.
Windows Server 2016 10.0
GC: G1 Young Generation, G1 Old Generation