-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
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
Inconsistency between function and non-function scope binding #74
Comments
Hey Chris, The expectation is only invokable's i.e. Components and helpers are retrieved from scope. We can potentially add some docs clarifying this. The VM currently only lets us resolve invokable's and not necessarily any free variables in scope. Chirag |
Thanks for the quick reply! I think adding docs would help a bunch, and I can author a PR to that effect early next week if you like. I also think we should look at making tweaks to the VM, though, because the behavior here is quite surprising—and I expect it will be particularly surprising for anyone coming from e.g. React. |
Expected: any value in scope is accessible in templates.
Actual: functions in scope are accessible (as modifiers or helpers), but other values are not.
Here's a minimal reproduction playground.
The text was updated successfully, but these errors were encountered: