Mappr

Latest version: v0.4.1

Safety actively analyzes 681812 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 3

0.4.1

=======

Dev tasks
---------

- Update dev dependencies

0.4.0

=======

Features
--------

- Support extra context in the converters
You can pass extra context when converting between types. This means the
conversion function can grab values from both the source object and the extra
context. This is especially usefull when working with db records where source
type might just have a foreign key but the destination type has the whole
referenced object. Oftentimes you already have that object fetched so no need
to do the DB fetching inside the converter. You can just grab the object from
the extra context.
- Support for custom conversion functions

Dev tasks
---------

- Cache deps right after installation on the CI run

0.3.5

=======

Dev tasks
---------

- Move away from gitflow
- Update peltak to the latest version
- Update dev dependencies to the latest versions

0.3.4

=======

0.3.1

=======


Fixes
-----

- Allow specifying strategy on register

0.3.0

=======


Features
--------

- Can specify default strategy for the mapping
Until now, you could only specify the strategy during conversion, so if you
wanted to always use a SETATTR strategy you would have to pass it each time
you convert something. Now you can define the strategy when registering a
mapping and then it will be used as default for all conversions. You can
still override the strategy directly in `convert`, but the default is now
specified in the mapping.


Changes
-------

- The mapping functions do not take name anymore
The name is never used anyway and is always on the other side of ‘=‘ in the
mapping. No need to keep it and makes things longer. Getting rid of it to
simplify the mappers slightly.

Page 1 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.