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
And this warning message:
Warning: Can't call setState on a component that is not yet mounted. This is a no-op, but it might indicate a bug in your application. Instead, assign to this.state directly or define a state = {}; class property with the desired state in the c component.
It appears when the component mounts. The code does not break, it is just a warning, so it isn't a high priority issue, I am just telling you, it could be interesting.
Can anyone explain why is this happening?
I am using the currently newest version 1.15.0, but it appears in 1.14.7 too.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi!
I have the following code:
<Editor
editorState={editorStateEN}
onEditorStateChange={(e) => { setEditorStateEN(e) }}
/>
And this warning message:
Warning: Can't call setState on a component that is not yet mounted. This is a no-op, but it might indicate a bug in your application. Instead, assign to
this.state
directly or define astate = {};
class property with the desired state in the c component.It appears when the component mounts. The code does not break, it is just a warning, so it isn't a high priority issue, I am just telling you, it could be interesting.
Can anyone explain why is this happening?
I am using the currently newest version 1.15.0, but it appears in 1.14.7 too.
Thank you in advance!
Beta Was this translation helpful? Give feedback.
All reactions