-
Notifications
You must be signed in to change notification settings - Fork 1
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
App based on this sample #1
Comments
This is nice @delneg! Thanks for letting me know! Do you mean you have already used JSX in a real Fable app? If so, can you please link to the file containing the Fable JSX code? |
Well, I'm working it out. Right now I'm having troubles debugging what seems like "react-chat-elements" library issues, because of the React v17 vs React v18 differences & changes, and the fact new Fable setup that it doesn't work with React < 18. |
@alfonsogarciacaro |
Nice that you made it work with React 18. We can try to adapt useElmish to React 17, but it's a bit difficult without the new hook. Would it be ok to edit it the useElmish post to include a reference to your app? |
I don't know if it's necessary to backport useElmish to React 17, but just in case - can't the new hook be included in the useElmish itself, if it's a dependency ? Also, regarding the reference to the app - it would be great! |
Will do, thanks!
Ah, you're right! We can just polyfill the hook 😅 We can do that if there are other users that want to use Fable.React.UseElmish and cannot upgrade to React 18. |
Although I'm still debugging issues happening in runtime (which is currently pretty painful because I have to build it in production & replace django template base.html filenames, but I'll figure it out) - you probably might be interested because it's a pretty complex code, using all sorts of Fable features, new & old.
The app itself is a F# React frontend for a Django-based chat backend plugin, which was previously written in part js / part F#, but now is 100% F#.
Bearle/django_private_chat2#41
@alfonsogarciacaro
The text was updated successfully, but these errors were encountered: