We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Edge case note that it's not a bug but we'd like to improve user XP when this happens
Repro : 1/ having some kind of StreamBuilder with firebase for example
StreamBuilder
(m/StreamBuilder :stream stream :builder (fn [_ snapshot] (let [connection-state (.-connectionState snapshot)] (if (or (== connection-state m.ConnectionState/none) (== connection-state m.ConnectionState/waiting)) login (if (== connection-state m.ConnectionState/done) (m/Text "Don't know what to do here") (if-some [user (.-data snapshot)] main-app login))))))
2/ then your login is a stateful widget with focus-node and a TextField for example
TextField
(f/widget :with [focus-node-email (m/FocusNode) focus-node-password (m/FocusNode)])
3/ dispose will be call but focus-node will still be used after-all creating a sucky exception
Temporary solution : wrap the stateful widget in a stateless one (f/widget my-stateful-widget)
(f/widget my-stateful-widget)
The text was updated successfully, but these errors were encountered:
Can you make a self contained runnable minimal repro?
Sorry, something went wrong.
(def my-widget (f/widget ...)) of stateful widgets seems to be problematic.
(def my-widget (f/widget ...))
At that time I was mislead, it's not a state problem but it's how we update streams
No branches or pull requests
Edge case
note that it's not a bug but we'd like to improve user XP when this happens
Repro :
1/ having some kind of
StreamBuilder
with firebase for example2/ then your login is a stateful widget with focus-node and a
TextField
for example3/ dispose will be call but focus-node will still be used after-all creating a sucky exception
Temporary solution :
wrap the stateful widget in a stateless one
(f/widget my-stateful-widget)
The text was updated successfully, but these errors were encountered: