These are chat archives for canjs/canjs
if you want to rule out auto-mount, you can break right here: https://github.com/canjs/can-view-callbacks/blob/731d4fe9cfb3998e2a382db07561f60dc917bca9/can-view-callbacks.js#L178
@phillipskevin Ok I got the issue. We started to implement new components using
can 4 those components used on the page with
can 2. And new components inside have inner components that have same names as components written in
So let's say on the page we have list with comments. And we have re-usable
<custom-textarea></custom-textarea> written in
After we added to this page new bundle with component about....feedbacks written on
can 4 and this components has updated version of
<cutom-textarea></custom-textarea> that using
can 4 already :(
custom-textarea and render
can4 component inside
can2 component :)
Maybe there is way to add some check that verify...
can 4+ components or i don't know some dericitive that tells to not touch this component.
There is global flag for this:
But maybe there is more... local approach so we can mark our
can 2 components.
Obviously there is way to... name them like
can4-custom-textarea but aaahhh... not really good.
Obviously there is way to... name them like can4-custom-textarea but aaahhh... not really good.