-
-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
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
Questionable addEventListener "fix" #458
Comments
Confirmed that the latest version does fail in RN. Produces this error from the
|
No good reason, just lack of familiarity with React Native :-) If just catching would be preferable, I'll make that change now 👍 |
@yoodame Thank you Yaw! Do either of you maybe have a project you could recommend that's using both Sente and React Native? Would like to confirm that this is the only thing preventing RN support. |
I am currently working on an RN app with the latest Fulcro + Fulcro inspect tool. I've found 2 issues thus far. This one and another on encore - taoensso/encore#81 |
Verified that this fixes the error for RN as well. (tested both the new sente and encore version) |
Thanks for the quick response! |
Great news, and thanks for the quick confirmation! I'll cut Sente v1.20 final later today and include these fixes 👍 (Will keep this issue open till the release is out) |
Preparing v1.20 release now, closing. |
I was having the problem with addEventListener (electron/node) that this latest version fixes this way:
but I also use Sente in RN, and I'm pretty sure it will fail there too (unverified). Why not just wrap that in
catching
and forget about it? :D Or at least flip the condition to browser targets?The text was updated successfully, but these errors were encountered: