You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
…objects (handlebars-lang#1858)
- per issue handlebars-lang#1858
- adds cases for nested input objects to existing cases
- very minor refactor to re-use the same test logic, keep tests readable.
The fact that this workaround works also shows fixing this issue does not increase access / loosen security, it would just restore API consistency, treating nested objects the same regardless of access mode.
The other option would be to disallow the workaround. This would at least restore consistency to the security restriction.
vassudanagunta
added a commit
to vassudanagunta/handlebars.js
that referenced
this issue
May 9, 2022
…objects (handlebars-lang#1858)
- per issue handlebars-lang#1858
- adds cases for nested input objects to existing cases
- very minor refactor to re-use the same test logic, keep tests readable.
For example, given the following input:
the following,
should yield
'returnValue'
. Instead, it yields'undefined'
.PR with failing test-cases submitted: #1859.
The text was updated successfully, but these errors were encountered: