Jack Saunders
Jack Saunders
If you have min/max on a Decimal field, and you pass the value as a string (which is supposed to be supported,) a crash occurs. ```tests/test_pipelines/test_numeric.py:207: in test_decimal_input_bounds_when_passed_as_string field.marshal(mapper_session) kim/field.py:344:...
On marshal, session.mapper.parent and session.parent are populated. These are set in the function marshal_nested(). However, on serialize neither is set correctly as serialize_nested() does not do this. It should do...
## Description Roles provide user of Kim with a powerful way to control what fields should be included when marshaling or serialzing a Mapper. The ability to specify a role...
If you do: `blacklist(...) | whitelist(...)` The result is only the whitelist takes precedence but this is really non obvious. Either the behaviour should be changed to make things in...
`session.parent` can only be accessed in a collection: `field.Collection(field.Nested(SomeMapper))` it will be null in the case of a simple `field.Nested(SomeMapper)`
For example, if your application includes third party libraries that define their own Kim Mappers, you're likely to have conflicts with common names such as `User`. A simple workaround could...
``` name = field.String(source='full', required=True) @marshaling.processes('name') def print_name(session): print(session.data) mapper.marshal({}, partial=True, obj=existing_obj) ``` expected result: `session.data == existing_obj.full` actual result: `session.data == None`
Currently `self.fields` is in fact `cls.fields` and changes made to fields persist across all Mapper instances
Rather than having to add to extra_error_msgs
At the start of a three finger swipe gesture on trackpad, a small scroll event is generated and not suppressed. This results in the active window scrolling slightly every time...