-
Notifications
You must be signed in to change notification settings - Fork 34
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
More Playwright tests for custom forms page #303
Comments
@dantownsend Now that the array fields work, basically all fields work as expected (except the datetime field, but that can easily be solved by adding class CustomFormlModel(BaseModel):
boolean_field: bool
float_field: float
integer_field: int
string_field: str
list_field: t.List[str]
tuple_field: t.Tuple[str]
time_field: datetime.time
date_field: datetime.date
datetime_field: datetime.datetime |
@sinisaos Yeah, all possible fields is probably unrealistic as Pydantic potentially has so many different field types. I think the ones you've defined are OK, but I'd add |
@dantownsend Interesting, if we add |
@sinisaos On port 8000 it serves the compiled assets - so you'll have to run |
@dantownsend Yes you are right. I forgot to build after the admin UI changes. Thanks. I can make PR if you want? |
@sinisaos Yes, that would be good - thanks |
Related to #298
We could do with a mega form with all of the possible fields, and testing it with Playwright.
The text was updated successfully, but these errors were encountered: