select2 VS framework

Most people using react aren't building SPAs. Vue/React can be used the same way as jquery, which is to add enhanced UI functionality that server-side HTML views simply can't offer.

The best example is a multi-select box, or a searchable select box with autocomplete (what W3 calls the combobox pattern https://www.w3.org/WAI/ARIA/apg/patterns/combobox/) which in jquery was usually via https://select2.org/

For example, on my company website there's a timezone select box with are 151 options. Asking a user to simply scroll through 100+ to find theirs is annoying vs typing a few characters and hitting enter.

There's many examples of select boxes like that and there really is no static server-side way to solve this problem (I tried hard to think of one)... without creating a multi-page Wizard for what should be a single field on a larger form.

If you're building a SaaS product there are many highly-interactive components that demand JS and there's really no better mainstream solution atm than static-first sites with small "islands" of Vue/React style components (ideally with hydration) where interactivity is required.

People still abuse React/Vue of course, but the trend is 100% moving back to "mostly static" rather than slow SPAs and IMO JS-powered components are not never going away unless browsers start offering these complex components built-in.

I’m a fan of select2 (https://select2.org), it supports loading in data from a foreign source (API)

You could use a Select2() for the records which prevent the massive amount of data being transferred.

Sometimes I still import it for only one thing : select2 that depends on it. Does anyone have an alternative ? I'd love it

The traditional solution was to use ModelAdmin.raw_id_fields, a comma-delimited string of IDs in a text input. Many users found the interaction inelegant, and so ModelAdmin.autocomplete_fields with live search integration with Select2 was added in Django 2.0.

The module django-extensions has a searchable select box widget. There are others using Select2 as well.

I did implement PSR7 in the develop branch though.

https://github.com/Divergence/framework/blob/6af1b6b0e56b25c...

Where people go wrong is trying to do this field normalization logic inside their query builder. That leads to all sorts of problems. The query builder shouldn't know what is going on with your ORM at all. It's just gluing strings together to form a query.

You can see my dead simple query builder here: https://github.com/Divergence/framework/tree/develop/src/IO/...

I honestly used to not have one as it's so simple but decided it was a good abstraction to assimilate from other frameworks. My query builder does not attempt to sanitize anything. The ActiveRecord class takes care of that through the data mapping conversion functions for all the basic HTTP CRUD functionality.

If you believe you can find a security hole in my ORM I'm all ears.

I wrote my own like 10 years ago https://github.com/Divergence/framework/blob/release/src/Models/ActiveRecord.php