kim

kim copied to clipboard

Only one invalid field at a time

1

Currently only one invalid field can be reported at the time, because an exception is raised immediately after calling `.invalid()` It would be helpful if more than one could be...

kirknorthrop

Mapper class names in registry should not be required to be globally unique

1

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...

jackqu7

Some weird issue with the metaclass stuff in six was detected on version 1.6.1 ``` /home/vagrant/.virtualenvs/vizibl-api/local/lib/python2.7/site-packages/kim/__init__.py in () 7 8 ----> 9 from .mapper import Mapper 10 from .field import...

mikeywaites

``` 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`

jackqu7

Currently `self.fields` is in fact `cls.fields` and changes made to fields persist across all Mapper instances

jackqu7

Rather than having to add to extra_error_msgs

jackqu7