creating function scopes in `render` impacts performance about lucid HOT 5 CLOSED

I'm currently working on this one. Will have PR out today.

from lucid.

Also here's an article detailing the problem a bit more.

from lucid.

We're debating whether this should be simply value or something else entirely. I'm not a huge fan of using value cause I feel like it's overloaded and doesn't convey the purpose well in a React app. But it's still up for debate.

from lucid.

My thoughts on what value means and why I think it's an inappropriate prop name for radio/checkbox/item/button/option/etc:

value for input controls is data that should come from the user: like text/password/file/search/etc inputs. Names/IDs are supposed to be defined by the app for identification purposes within the app itself. However, using name or id as a prop name for input controls has some legacy technical/semantic value for certain HTML elements, so it doesn't feel right to repurpose those names (since lucid components pass them thru to the native elements anyways) so reasonably, something like uniqueId makes the most sense to me as a general solution which can be applied to any kind of repeatable component. Also having its default unique ID be the index position in a group eliminates the need to even specify it in most cases, so it's not a prop that will see a lot of direct use by a consumer.

from lucid.

We're considering returning all the props with a callback signature of ({ event, props }) => {}

from lucid.