-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
This makes the HTMX Component a pydantic.BaseModel #14
base: master
Are you sure you want to change the base?
Conversation
6c2dd94
to
b26cf8e
Compare
c095f08
to
fc9284e
Compare
I like the idea, because now when I create a base HTMX component I have to repeat its I will work on this proposal. |
9c65cc0
to
b762c99
Compare
The README needs to be updated. |
b762c99
to
78c8f86
Compare
I'm on the process of doing all of this. I went for the breaking change version, but even breaking the import which I find more dev-friendly because it won't even allow you to run the server while developing because an ImportError. This is still not ready yet. It will take some time to complete. |
ca49d08
to
1371db2
Compare
This is a breaking change. To avoid issues I have changed the name of the base Component to HTMXComponent, so errors are harder to get to production unnoticed.
We using syntax which is not available in Python 3.6, 3.7 nor 3.9. For instance, the union operator for dicts.
1371db2
to
e817da4
Compare
The implications are:
Component.template_name
->Component._template_name
Component.__init__
->Component.mount
The
__init__
is now handled by pydantic