#2393: Forms with nested schemas
---------------------------------------------+------------------------------
Reporter: guest | Owner: Chris Arndt
Type: defect | Status: assigned
Priority: normal | Milestone: 1.0.x bugfix
Component: TG Widgets | Version: 1.1
Severity: normal | Resolution:
Keywords: needs review, forms, FormEncode |
---------------------------------------------+------------------------------
Comment (by chrisz):
Replying to [comment:3 Chris Arndt]:
> It was only possible in !TurboGears to work around this because
`turbogears.validators.Schema` sets the `if_key_missing` attribute to
`None`, so when FE validates the data, it will just assign a `None` value
to those fields, i.e. you get `PersonalDetailsFields=None` in the data
with your example above.
>
> Why this isn't working anymore in FE > 0.7.1 I don't know. I think you
should raise this issue on the FormEncode mailing list.
Actually this is due to the formencode bugfix in changeset 3104 after
which is_empty() returns False by default. So it seems it worked only
because of a bug in formencode.
The patch looks good to me, but I think we don't need the change in
generate_schema(); the change in copy_schema() should be sufficient.
--
Ticket URL: <http://trac.turbogears.org/ticket/2393#comment:7>
TurboGears <http://www.turbogears.org/>
TurboGears front-to-back web development
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google
Groups "TurboGears Tickets" group.
This group is read-only. No posting by normal members allowed.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/turbogears-tickets?hl=en?hl=en
-~----------~----~----~----~------~----~------~--~---
