Shared Endpoint for Dynamic Queries

[Alex-Sichkar]

Is it possible to consider implementing optional support for a shared endpoint for widgets like Selectize, DatePicker, etc., in future releases, similar to how django-select2 does? This would enable the use of function-based views.

[jrief]

But then the developer must add that endpoint to his own URL routing. The way it is implemented now avoids this and reuses the existing endpoint required anyway in order to render the specific widget.

I also would like to keep the endpoints for say, the Selectize- and the FileUpload-widget separate.

Where do you need function based views which can not be handled by class-based views.

[Alex-Sichkar]

I'm asking because I personally don't like Django's implementation of CBVs, and many others feel the same. All those mixins are not very intuitive, to say the least, in my opinion. This would make using django-formset much more flexible overall, while also making it easier for people like me who prefer alternatives to Django’s built-in CBVs.