4 ms·

Does React really need something like this? This seems to just be following the "plugin" tradition set forth by jQuery. I've written a lot of React and haven't

Does React really need something like this? This seems to just be following the "plugin" tradition set forth by jQuery. I've written a lot of React and haven't found myself needing things like this. It's just JavaScript and markup people, you should be able to do it yourself rather easily.

asolove 12y ago
Building really good complex form widgets is hard work. You have to handle ARIA/accessibility, ensure you have support for focus and tabbing, handle lots of keyboard shortcuts as appropriate, etc. Solid implementations of autosuggest inputs, token input fields, or fast scrolling tables can run into the thousands of lines. Having reusable versions of them would be very helpful for the React ecosystem.
fiatjaf 12y ago
I'm also afraid of the jQuery effect.
hcarvalhoalves 12y ago
It's really easy to make reusable React components though, the boundaries are well defined (props) and the state is confined to the child. Pretty much what Web Components aspires to be, but it already works and you can leverage today. I have a couple components I can extract from a running project and publish there without any changes (Google Maps, Google Autocomplete, Tagging input, ...) and it will just work.
- kylemathews 12y ago
  Please do publish them! A great react-google-maps I'd definitely use.
  - hcarvalhoalves 12y ago
    I'll publish soon. You might want to follow on Github: http://github.com/hcarvalhoalves http://github.com/hcarvalhoalves
rexxars 12y ago
It doesn't need it, but I don't see how it is possibly a bad thing? Do you want a textarea that adjusts size based on the content? Sure, you could write that yourself, or you could just `npm install react-textarea-autosize`. Want to render a sparkline of some data? Sure, you could mess around with existing libs and see if you can get them to work nice with React, or you could just pull in something you can expect actually works, like react-sparkline.

asolove 12y ago

Building really good complex form widgets is hard work. You have to handle ARIA/accessibility, ensure you have support for focus and tabbing, handle lots of keyboard shortcuts as appropriate, etc. Solid implementations of autosuggest inputs, token input fields, or fast scrolling tables can run into the thousands of lines. Having reusable versions of them would be very helpful for the React ecosystem.

fiatjaf 12y ago

I'm also afraid of the jQuery effect.

hcarvalhoalves 12y ago

It's really easy to make reusable React components though, the boundaries are well defined (props) and the state is confined to the child. Pretty much what Web Components aspires to be, but it already works and you can leverage today. I have a couple components I can extract from a running project and publish there without any changes (Google Maps, Google Autocomplete, Tagging input, ...) and it will just work.

kylemathews 12y ago
Please do publish them! A great react-google-maps I'd definitely use.
- hcarvalhoalves 12y ago
  I'll publish soon. You might want to follow on Github: http://github.com/hcarvalhoalves http://github.com/hcarvalhoalves

rexxars 12y ago

It doesn't need it, but I don't see how it is possibly a bad thing? Do you want a textarea that adjusts size based on the content? Sure, you could write that yourself, or you could just `npm install react-textarea-autosize`. Want to render a sparkline of some data? Sure, you could mess around with existing libs and see if you can get them to work nice with React, or you could just pull in something you can expect actually works, like react-sparkline.