You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The use of of unicorn:model has always struck me as confusing considering it has nothing to do with regular Django Models. It was named that way since it followed in the footsteps of Vue and Livewire, but I think there could be a more descriptive word that is used.
My leading contender would be unicorn:bind.
How could it be implemented/designed?
I would make this backwards-compatible so that unicorn:model would still be valid, but change all documentation to reference unicorn:bind.
Why do we need this improvement?
The use of of
unicorn:model
has always struck me as confusing considering it has nothing to do with regular Django Models. It was named that way since it followed in the footsteps of Vue and Livewire, but I think there could be a more descriptive word that is used.My leading contender would be
unicorn:bind
.How could it be implemented/designed?
I would make this backwards-compatible so that
unicorn:model
would still be valid, but change all documentation to referenceunicorn:bind
.Will this be a breaking change?
Have you read the Contributing guidelines?
Are you willing to work on this issue?
The text was updated successfully, but these errors were encountered: