Readit NewsI think it'd be worth looking at what's already out there before you put a lot of effort into this, unless of course this is merely for fun/learning.
aleclarsoniv commented on Cash: A small jQuery alternative for modern browsers github.com/fabiospampinat... · Posted by u/thunderbong
I used this initially in a browser extension I'm building. Ended up migrating to a JSX library instead, because jQuery turns into hard-to-reason-about code pretty quickly once you're past “simple app” territory (and I say this as someone who wrote my own jQuery-inspired library[1]). Right tool for the job, as they say.
[1]: https://github.com/aleclarson/dough
P.S. If you can cope with jQuery in a medium/large app, good for you. But it's not my cup of tea.
Is this usable as a package installable from NPM?
I just published it now: https://www.npmjs.com/package/@json-qs/json-qs
Is there an example where passing full JSON objects as a query string would be the right solution?
The most common case is probably complex search queries. It's really nice not having to flatten your data just to get network level caching.
In my case, building an RPC library with REST semantics, it's important to me to not place any restrictions on how developers pass their data to the backend. So removing that arbitrary flattening requirement is a big win. The json-qs specification does it in a way that balances readability and compactness.
If anyone has any feedback on the design, I'd be interested in hearing it. Or if you have questions about design choices, I can answer them. Thanks for reading!
[1]: https://github.com/scrollback/juri