Ocdsmerge

Latest version: v0.7.0

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

Scan your dependencies

Page 2 of 5

0.6.1

------------------

Changed
~~~~~~~

- Improve performance.

0.6.0

------------------

Changed
~~~~~~~

- **Backwards-incompatible:** Replace ``merge`` and ``merged_versioned`` functions with :class:`ocdsmerge.Merger` class.

Fixed
~~~~~

- ``rule_overrides`` keys omit array indexes.

0.5.12

-------------------

Fixed
~~~~~

- ``MissingDateKeyError`` is now initialized correctly.

0.5.11

-------------------

Changed
~~~~~~~

- ``MissingDateKeyError`` inherits from ``KeyError``, and ``NonObjectReleaseError``, ``NullDateValueError`` and ``NonStringDateValueError`` inherit from ``TypeError``, to allow exception handling of versions less than 0.5.2 to remain unchanged.

0.5.10.post3

-------------------------

Changed
~~~~~~~

- The collision behavior is changed to always warn.
- Remove the ``collision_behavior`` argument. Use a `warning filter <https://docs.python.org/3/library/warnings.html>`__ instead.
- Add ``path`` and ``id`` properties to ``DuplicateIdValueWarning`` to store the ``path`` at which, and the ``id`` on which, the collision occurred.

0.5.10.post2

-------------------------

Changed
~~~~~~~

- Add a ``rule_overrides`` argument to ``merge``, ``merge_versioned``, ``add_release_to_compiled_release`` and ``add_release_to_versioned_release``, which can be set on a per-field basis to:

- ``ocdsmerge.MERGE_BY_POSITION``: merge objects in the array based on their array index, instead of their ``id`` value.
- ``ocdsmerge.APPEND``: retain all objects in the array.

- Remove these flags as possible values of ``collision_behavior``.

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.