Stephan Richter wrote:
On Friday 17 March 2006 03:23, Andrius Armonas wrote:
did "records" converter behaviour changed anyhow in zope3 since zope2?
No, this code has not been touched as far as I remember.
About 2 years ago I made a massive refactoring for
zope.publisher.browser.BrowserRequest and added some tests based on the
implementation.
But nobody I know
uses ":records", so it is probably under-tested.
Maybe we need some "converters simplification" so for example we can get rid of
some unused converters?
If we have this:
<input type="text" name="a.x:records:int" value="5" />
<input type="text" name="a.y:records:int" value="51" />
<input type="text" name="a.x:records:int" value="6" />
<input type="text" name="a.y:records:int" value="61" />
Then after form submit we get (in zope3):
a: ['x': 5, 'y': 51, 'x': 6, 'y': 61]
This is not valid Python.
It's just custom representation for zope.publisher.browser.Record object.
--
Dmitry Vasiliev (dima at hlabs.spb.ru)
http://hlabs.spb.ru
_______________________________________________
Zope3-users mailing list
[email protected]
http://mail.zope.org/mailman/listinfo/zope3-users
