You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After making an HTTP request for a page's HTML using axios, I am replacing the current page's HTML markup with the markup from the response of the request I made with vanilla JS. However, I am noticing this warning, [portal-vue]: source source already exists, and I am not too sure if I need to be very concerned about this warning log.
I've looked at the source and where the registerSource function is invoked to better understand the warning. Just before replacing the old markup with the new markup I am querying the old markup and passing $destroy() to the "old" components. Based on what I can tell from the source I have linked, portal-vue will "unregister" the components before they are destroyed. I was hoping that effectively unregistering components on the page would suppress the warning log -- [portal-vue]: source source already exists -- but that does not seem to have stopped the log from firing.
Are there more components for me to $destroy from the old markup that I am replacing? Is destroying old components the way to go in order to resolve the above warning -- if not, what way is the correct way to resolve the above warning?
Should I be concerned about the warning in general?
The text was updated successfully, but these errors were encountered:
After making an HTTP request for a page's HTML using axios, I am replacing the current page's HTML markup with the markup from the response of the request I made with vanilla JS. However, I am noticing this warning,
[portal-vue]: source source already exists
, and I am not too sure if I need to be very concerned about this warning log.I've looked at the source and where the
registerSource
function is invoked to better understand the warning. Just before replacing the old markup with the new markup I am querying the old markup and passing$destroy()
to the "old" components. Based on what I can tell from the source I have linked,portal-vue
will "unregister" the components before they are destroyed. I was hoping that effectively unregistering components on the page would suppress the warning log --[portal-vue]: source source already exists
-- but that does not seem to have stopped the log from firing.Are there more components for me to
$destroy
from the old markup that I am replacing? Is destroying old components the way to go in order to resolve the above warning -- if not, what way is the correct way to resolve the above warning?Should I be concerned about the warning in general?
The text was updated successfully, but these errors were encountered: