I’m trying to extend a 3rd party object to use as a component viewModel and the class is already using the method name “created”. Is there a way to still have access to the built in lifecycle methods while changing the name?
I was at least able to get around this by making a reference to the original in the constructor and creating an auCreate function which gets set to created. Once the auCreate function runs I set created back to the original.
It appears Aurelia 2 took this same approach. all lifecycle methods should have been prefixed with au or something to avoid any name collision.