What is the difference between using @model and this.model in a route template?
I encountered a bug in our codebase today and noticed two route templates were making use of the same component hierarchy so traced the issue back to the template that was passing the model to the components as @model i.e. @entries=@model.entries.
The issue was the Assertion Failed:
Attempting to update a value after using it in a computation can
cause logical errors, infinite revalidation bugs, and performance
issues, and is not supported.
For a reason I’m not understanding, it seems that converting the usage to this.model in the route template fixed the issue for me.
Ember Version: 3.20.6 LTS
2 posts - 2 participants