lorinkoz / django-js-choices Goto Github PK

It's cool that this automatically resolves the choices names conflicts. But, if you add a new choice or a package with a choice that collides with yours then the short name will be removed without notice. I think will be useful to select what names you want to make available so in advance you always know what model's choices you are using.

Cut new version with the following changes:

• Remove Python 2 compat.
• Remove Django <2 compat.
• Remove embedded rjsmin and provide as extra package.
• Add tests

I'd like the ability to add new sources of "choices" that are not from django models fields directly, but instead like some value,label pairs used for some custom logic that are not on any models and wants to be synced to a javascript frontend; I think django_js_choices would be a good place to put such logic.

I would imagine it to be something like this:

from django_js_choices import register_source

# some variable with value,label keys
DOABLE_ACTIONS = [("nothing", "Do nothing"), ("go_2", "Advance 2 steps"), ...]

register_source("doable_actions", DOABLE_ACTIONS)

What do you think? I'd be down for filling a PR for it.