Extension doesn't understand references containing env variables

[Palid]

Your environment

op-vscode version: 1.0.5

VS Code version:
Version: 1.99.3
Commit: 17baf841131aa23349f217ca7c570c76ee87b957
Date: 2025-04-15T23:18:46.076Z
Electron: 34.3.2
ElectronBuildId: 11161073
Chromium: 132.0.6834.210
Node.js: 20.18.3
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.3.0

CLI version: 2.30.3

OS: MacOS (irrelevant)

Steps to reproduce

Part 1:

1. Have a secret reference with a variable, e.g. op://MY_VAULT//${MY_ENVIRONMENT_NAME}/SECTION1/MY_SECRET_PASSWORD
2. Expect that 1password extension can understand the references and resolve the URL (it doesn't understand the reference, it's unclickable).
3. After resolving ${MY_ENVIRONMENT_NAME} manually to, let's say, develop, the link is now clickable.

Additionally, there's no way to provide any environment variables directly to the vscode extension in any other way than global environments, which is quite undesirable.

Same happens if you define it with a default env, e.g. op://MY_VAULT//${MY_ENVIRONMENT_NAME-PRODUCTION}/SECTION1/MY_SECRET_PASSWORD

What happened?

Secret reference with a declared env is not clickable, The Extension doesn't understand it correctly and suggests saving in 1password.

What did you expect to happen?

1password extension can understand the references and resolve the URL instead of suggesting to save it.

Notes & Logs