Skip to content
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

Elm Components #41

Open
dotnetspec opened this issue Jun 19, 2024 · 0 comments
Open

Elm Components #41

dotnetspec opened this issue Jun 19, 2024 · 0 comments

Comments

@dotnetspec
Copy link

I proposed this bounty.

It's quite possible my suggested framework, Elm:

Proposed Frameworks/Components/Libraries:
Elm: For adapting the user interface and handling network communications.

Would contravene this from the guidelines:
"Changes must be done 'the right way'. No hacks to make things work, if you are having issues, let the other devs know, so that we can help you out."

I'm not expecting to hack, but my experience is in Elm more than React and I have no interest in returning to React development. I fully understand if the project team do not want me to add Elm components to the existing React code to complete the bounty, but please confirm if Elm is acceptable or not so I don't waste time attempting the integration if it won't ultimately be accepted, whether it works or not. thanks ...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant