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
When using the webComponentConstructed lifecycle hook to get a reference to the component once it is constructed an error is thrown on line 32 of index.js. The webComponentConstructed function works as intended, but having this error apear in the console is not desirable.
The text was updated successfully, but these errors were encountered:
I also ran into this and haven't found a satisfying workaround yet. This error (probably) does not come from the webComponentConstructed, but the whole implementation itself. At least in my case, this error (probably) comes from the parent site giving attributes to the component before the component has been fully rendered. The error happens because appInstance (your react class) is defined after the component has been fully rendered (asynchronous rendering in index.js line 48) but the callback methods are immediately available (because they are defined this way).
In this case removing the webComponentConstructed method probably makes the rendering slightly faster allowing it to finish before the attributes are passed to component leading to this kind of behaviour. Or at least this is how it seems to me.
When using the webComponentConstructed lifecycle hook to get a reference to the component once it is constructed an error is thrown on line 32 of index.js. The webComponentConstructed function works as intended, but having this error apear in the console is not desirable.
The text was updated successfully, but these errors were encountered: