refactor(text-binding): always evaluate expressions in strict mode #1801
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📖 Description
Currently all bindings are evaluating expressions in strict mode, and have proved to be working fine for applications migrating from v1. Text binding (content binding), however, was not using this strict by default mode as there could be some bug regards to how null/undefined are handled.
This exception creates a discrepancy that is hard to explain, also there's not a lot of benefits doing this. Remove this behavior.
This open the way for us to remove non-strict mode in expression evaluation, as optional syntaxes are already supported. Though this will be another follow up PR.
Closes #1769 #1798