-
Notifications
You must be signed in to change notification settings - Fork 21
ModelStream as Mixin? #60
Comments
You make good points. Let me mull that over. Thanks. |
Thanks. I've searched for years for such a project. Already experimented with sockpuppet, HTMX, unpoly, Unicorn, alpine.js and some others. And turbo-django is definitely the best, hands down. Really great software, very clean design. |
Ah, and: You could even keep the class ModelStreamMixin:
...
class ModelStream(ModelStreamMixin, Stream):
pass
class ModelStreamComponent(ModelStreamMixin, BaseComponent):
pass Maybe you find better names. |
I'm coming from a similar place. I think this tech has extraordinary potential, just needs some polish and as you mentioned, clear documentation and examples. I'll keep chipping away at it, and hopefully the community will join in help sell more people on this project. |
I do not get the full purposes of ModelStream and Component, docs are not fully comprehensive for me here. If I understand correctly, you can add a
Meta
class to any Stream (even Component?) with amodel
attribute, and Turbo will connect pre_save/_delete etc. signals to that model.Then why do you have a ModelStream class to inherit from?
Wouldn't it be possible to implement ModelStream as Mixin? So you can add it to a
Component
too?Or am I thinking wrong here?
The text was updated successfully, but these errors were encountered: