We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OS: Win10 Build Version: 20230312.2
Repro Steps:
{ "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "parameters": { "int": { "type": "string", "metadata": { "description": "description" } }, "intOptional": { "type": "int", "defaultValue": 123 }, "string": { "type": "string", "metadata": { "description": "description" } }, "stringOptional": { "type": "string", "metadata": { "description": "description" }, "defaultValue": "hello" } }, "functions": [], "variables": {}, "resources": [], "outputs": {} }
{ "$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#", "contentVersion": "1.0.0.0", "functions": [], "variables": {}, "resources": [ { "name": "linkedDeployment1", "type": "Microsoft.Resources/deployments", "apiVersion": "2020-06-01", "properties": { "mode": "Incremental", "templateLink": { "relativePath": "childTemplate.json", "contentVersion": "1.0.0.0" }, "parameters": { } } } ], "outputs": {} }
Expect: The editor navigates to the definition of the parameter name.
Actual: The editor doesn't navigate to the definition of the parameter name.
The text was updated successfully, but these errors were encountered:
Not a regression. Looks like it should be pointing to the child.json URI but is pointing to main.json.
Sorry, something went wrong.
No branches or pull requests
OS: Win10
Build Version: 20230312.2
Repro Steps:
Expect:
The editor navigates to the definition of the parameter name.
Actual:
The editor doesn't navigate to the definition of the parameter name.
The text was updated successfully, but these errors were encountered: