I’m currently using a routing pattern that leverages routing parameters and the
activate() lifecycle method. When reading through the HTML Behavior Lifecycle section of the documentation, I noticed that the
activate() method isn’t included. This leads me to believe that my architecture is a little off the beaten path.
In my application, I have a large hierarchical list of assets. When clicked, the id for the clicked asset is sent through the route to the HTML Behavior via parameters. The component reads the parameter and fetches the appropriate data from my data store in the
activate() method. Am I using an anti-pattern by relying on the
activate() method to retrieve my model data? Is there more “Aureliative” way of sending model information to HTML Behaviors?