Parameter of type scope in scripted effects breaks highlighting/does not get inferred by what is passed

[adriangaro]

$from$ is a scope here passed so i can be easily passed and changed to correct scope. syntax highlighting breaks inside it.

[DragonKnightOfBreeze]

The logic to get the CWT config of $from$ is to be determined.

[adriangaro]

Well yes, but in this case $from$ is a parameter, not the scope from so it could be whatever is passed as to said parameter.

[DragonKnightOfBreeze]

We CANNOT get the actual config context in $from$ = {...} because $from$ can be anything, and I think it's unsuitable to infer what $from$ can be by checking all it's usages, to get the inferred config context.

[adriangaro]

Not necessarily to infer the scope type, but mostly fix the highlighting inside it, since no highlighting, nor autocomplete works inside the brackets if changing scope this way.

[DragonKnightOfBreeze]

Shall be reselved by inference from custom cwt configs, but never from usages.