You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From what I can see it is not possible to force-open the references view. Whether or not that view is opened when calling the command editor.action.showReferences seems to depend on the setting references.preferredLocation, which is set to peek by default. I'd like a way to ignore this setting and force-open the references view, for example through a dedicated command. My use case is implementing a custom command in the Svelte for VS Code extension which in the end should open this view.
It seems you may want this behavior, too, since right now "find file references" is implemented by temporarily switching the user config from "peek" to "view", which creates an empty vscode setting folder/file in the workplace if none exists already, which feels buggy (#134405 would solve this, too, for you, but wouldn't solve my problem)
Searched for: references force view
The text was updated successfully, but these errors were encountered:
From what I can see it is not possible to force-open the references view. Whether or not that view is opened when calling the command
editor.action.showReferences
seems to depend on the settingreferences.preferredLocation
, which is set topeek
by default. I'd like a way to ignore this setting and force-open the references view, for example through a dedicated command. My use case is implementing a custom command in the Svelte for VS Code extension which in the end should open this view.It seems you may want this behavior, too, since right now "find file references" is implemented by temporarily switching the user config from "peek" to "view", which creates an empty vscode setting folder/file in the workplace if none exists already, which feels buggy (#134405 would solve this, too, for you, but wouldn't solve my problem)
Searched for: references force view
The text was updated successfully, but these errors were encountered: