Adding "correct" suggestions to scope walking warning
·
604 commits
to master
since this release
Some examples of what the warning looks like now:
public/app/app.stache:46: "environment" is not in the current scope, so it is being read from a parent scope.
This will not happen automatically in an upcoming release. See https://canjs.com/doc/can-stache.scopeAndContext.html#PreventingScopeWalking.
Use "../../environment" or "scope.find('environment')" instead.
public/app/environment-manager/common/multi-select/multi-select.stache:18: "hasOption" is not in the current scope, so it is being read from a parent scope.
This will not happen automatically in an upcoming release. See https://canjs.com/doc/can-stache.scopeAndContext.html#PreventingScopeWalking.
Use "scope.root.hasOption" or "../hasOption" or "scope.find('hasOption')" instead.
public/app/environment-manager/common/pagination-limit/pagination-limit.stache:3: "limit" is not in the current scope, so it is being read from a parent scope.
This will not happen automatically in an upcoming release. See https://canjs.com/doc/can-stache.scopeAndContext.html#PreventingScopeWalking.
Use "scope.root.limit" or "../limit" or "scope.find('limit')" instead.