Leo Y. Li

+1 And I think it should be addressed in the user guide before the enhancement is done... it confused some how...

I'm also wonder as if this project is still active... the suggestion to add the support for `ListFormat` can be handy though...

There are full of middleware in Node.js/Express. lol... It's really powerful!

@crimx, thanks for the works! However, wasn't the library still looks a bit too complicated?! I mean, do we really need to recreate state management over and over again?! Putting...

@crimx, perhaps. But as long as I see `const [onChange, textChange$] = useObservableCallback`, I recognize this opens the door to pass observable as props, which should be an anti-pattern. That...

@crimx, right. I think your solutions covers the entire use case if we just want to use React + RxJS and make everything observable, which is really nice. And surely...

Yes, I have also received this `selector-type-no-unknown` error... Here is my work around: ```json "rules": { "selector-type-no-unknown": [true, { "ignoreTypes": ["/^-styled-mixin/"] }] }, ```

@chinesedfan, can be considered to add my workaround into the recommended setup? I mean people using it expect it can also take care about all valid use case.

Ok, if `a[]` is always treated as an independent new item, then the following result met my expectations. ```javascript qs.parse('a[]=1&a[0]=2&a[]=3') === { a: [ '1', '3', '2' ] } //...

@ljharb Yeah I see. I currently just added a function to modify the result from `qs.parse()` in my express app for recursivly handling the **last-one-win** case (so that I don't...