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
I really admire the time and effort you guys have put into this project, and I want to contribute to it. The feature idea is not mine, but from the team leader of my project, who wants to use remix-froms but needs an array input in the application.
The difficulty with an array input is that it is not really natively supported by HTML (apart from using multiple inputs or separating by some delimiter, which are both inelegantly). To still make it work without JS, I would propose the following:
The input sends a request to an API whenever an element is added or removed, the API then returns the form element just with an updated list of the elements inside. That way for the developers it just works and is a very convenient feature, even outperforming the native HTML in a clean manner. The only drawback might be a bit more traffic, but that shouldn't be any problem.
I don't know if you saw, but a while ago I already thought about how to implement something like that and also created a prototype version (see here), but in the end it just didn't feel right.
Hi there,
I really admire the time and effort you guys have put into this project, and I want to contribute to it. The feature idea is not mine, but from the team leader of my project, who wants to use remix-froms but needs an array input in the application.
The difficulty with an array input is that it is not really natively supported by HTML (apart from using multiple inputs or separating by some delimiter, which are both inelegantly). To still make it work without JS, I would propose the following:
The input sends a request to an API whenever an element is added or removed, the API then returns the form element just with an updated list of the elements inside. That way for the developers it just works and is a very convenient feature, even outperforming the native HTML in a clean manner. The only drawback might be a bit more traffic, but that shouldn't be any problem.
https://www.youtube.com/watch?v=w2i-9cYxSdc&list=PLXoynULbYuEDG2wBFSZ66b85EIspy3fy6&index=4 -> This as a native input type without a database behind but instead as a kind of "recursive" element
I would appreciate if we could work together to make this work and to hear feedback from you.
Thanks in advance <3
The text was updated successfully, but these errors were encountered: