const string value as map key?

imants_smidchens

Hi! I'm working on a featurescript that has a lot of maps for user inputs/calculations, and to keep things clean & organized, I've moved all the maps to a separate feature studio, which I then import.

To make things more robust & future proof, I'm defining some strings (which will be used in keys later) as constants, but unfortunately Featurescript insists that it can't find a key then.

for example:

const a = "foo";
const b = "bar";
export const DemoTable = {
   "name" : "table",
   "displayName" : "table",
   "default" : (a)
   "entries" : {
      (a) : "chose foo",
      (b) : "chose bar",
   }
}

If I use strings for the keys, it works fine, but changing them to variables, even when wrapped in parentheses, results in the Feature Studio that imports these tables saying "Map entry has no key"
supposedly this should be allowed....





any suggestions?

ilya_baran

It looks correct, other than missing a comma after

"default" : (a)

and a missing a semicolon at the end.  Public doc version that shows the error?

imants_smidchens

https://cad.onshape.com/documents/7e9ed67b52e115f7d48a0059/w/bcb370c431cbc27f53179a14/e/c80a7d5ed92a33d2029c9fda

kevin_o_toole_1

Your code is fine to use in FeatureScript runtime code, but defining FS parameters (in this case, a lookup table) requires specific syntax, since parameter definitions need to created before the code is run.

So lookup tables specifically require their maps to be listed with literal string keys, not an arbitrary FeatureScript expression.

imants_smidchens

kevin_o_toole_1 said:

Your code is fine to use in FeatureScript runtime code, but defining FS parameters (in this case, a lookup table) requires specific syntax, since parameter definitions need to created before the code is run.

So lookup tables specifically require their maps to be listed with literal string keys, not an arbitrary FeatureScript expression.

Gotcha. Thanks for the info!