v0.38.x breaks extendableParamFiles feature when using imports in nested .bicepparam files

[jamesharling]

Bicep version
v0.38.x

Describe the bug
If a nested bicepparam file has params that are bound to an imported function or variable, the intellisense and build fails with the error:

Message: Internal Error - System.ArgumentException: Unable to determine parent of specified node of type 'PropertyAccessSyntax' at span '[722:754]' because it has not been indexed.

This was working in previous versions, i.e. v0.37.x and older.

To Reproduce
lookups.bicep

@export()
var subscriptions = {
  mySub: {
    id: '5f6cc39d-14a2-4f45-85b3-46a7b9e147d8'
  }
}

core.bicepparam

import { subscriptions } from 'lookups.bicep'

param subscriptionId = subscriptions.mySub.id

main.bicepparam

using './main.bicep'

extends 'core.bicepparam'

Additional context
Add any other context about the problem here.

[polatengin]

I repro "almost" the same issue reported;

// main.bicep
param subscriptionId string

// lookups.bicep
@export()
var subscriptions = {
  mySub: {
    id: '5f6cc39d-14a2-4f45-85b3-46a7b9e147d8'
  }
}

// core.bicepparam
using none
import { subscriptions } from 'lookups.bicep'
param subscriptionId = subscriptions.mySub.id

// main.bicepparam
using './main.bicep'
extends 'core.bicepparam'

Compiling main.bicepparam throws BCP338;

$ dotnet run --project ./src/Bicep.Cli -- build-params ./main.bicepparam

WARNING: The following experimental Bicep features have been enabled: Enable extendable parameters. Experimental features should be enabled for testing purposes only, as there are no guarantees about the quality or stability of these features. Do not enable these settings for any production usage, or your production environment may be subject to breaking.
/workspaces/bicep/main.bicep(1,7) : Warning no-unused-params: Parameter "subscriptionId" is declared but never used. [https://aka.ms/bicep/linter-diagnostics#no-unused-params]
/workspaces/bicep/main.bicepparam(4,35) : Error BCP338: Failed to evaluate parameter "subscriptionId": The given key 'Bicep.Core.Semantics.ImportedVariableSymbol' was not present in the dictionary. [https://aka.ms/bicep/core-diagnostics#BCP338]

If we switch to the PR branch (#18223) I created to fix a similar issue (#18221) and run the build-params command again, it doesn't fail;

$ dotnet run --project ./src/Bicep.Cli -- build-params ./main.bicepparam

WARNING: The following experimental Bicep features have been enabled: Enable extendable parameters. Experimental features should be enabled for testing purposes only, as there are no guarantees about the quality or stability of these features. Do not enable these settings for any production usage, or your production environment may be subject to breaking.
/workspaces/bicep/main.bicep(1,7) : Warning no-unused-params: Parameter "subscriptionId" is declared but never used. [https://aka.ms/bicep/linter-diagnostics#no-unused-params]

Although I couldn't get the error message reported in the issue Message: Internal Error - System.ArgumentException: Unable to determine parent of specified node of type 'PropertyAccessSyntax' at span '[722:754]' because it has not been indexed. , I believe it's fixed with my other PR (#18223)

I'll re-check this issue after my PR is merged.

[peter-de-wit]

Got the same problem @jamesharling . I think they have updated the Azure DevOps agent image/ pipeline tasks or AZ powershell which pushed the newest version of bicep. BICEP that worked perfectly on Thursday is broken since Friday.

[jamesharling]

@polatengin in which release can we expect this fix to be available?

[polatengin]

Since the PR that fixes this issue is merged already, I assume in the next release.

It must be the v0.39, but let's ask @stephaniezyen for confirmation.

[stephaniezyen]

@jamesharling yes this will be in the v0.39 release which we hope to release by end of next week :)