dir-content-diff 1.14.1__tar.gz → 1.15.1__tar.gz

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.auto-changelog-template.hbs

@@ -120,7 +120,7 @@ Example Definitions
         - {{message}} ({{author}}{{#if href}} - [#{{id}}]({{href}}){{/if}})
       {{/commit-list}}
 
-      {{#commit-list merges heading='### Changes to Test Assests' message='^[tT]est:|^[tT]est\(' exclude='[bB]reaking [cC]hange:|[bB]reaking:|\[skip-changelog\]'}}
+      {{#commit-list merges heading='### Changes to Test Assets' message='^[tT]est:|^[tT]est\(' exclude='[bB]reaking [cC]hange:|[bB]reaking:|\[skip-changelog\]'}}
         - {{message}} ({{author}}{{#if href}} - [#{{id}}]({{href}}){{/if}})
       {{/commit-list}}
 
@@ -174,7 +174,7 @@ Example Definitions
         - {{subject}} ({{author}}{{#if href}} - [{{shorthash}}]({{href}}){{/if}})
       {{/commit-list}}
 
-      {{#commit-list commits heading='### Changes to Test Assests' message='^[tT]est:|^[tT]est\(' exclude='[bB]reaking [cC]hange:|[bB]reaking:|\[skip-changelog\]'}}
+      {{#commit-list commits heading='### Changes to Test Assets' message='^[tT]est:|^[tT]est\(' exclude='[bB]reaking [cC]hange:|[bB]reaking:|\[skip-changelog\]'}}
         - {{subject}} ({{author}}{{#if href}} - [{{shorthash}}]({{href}}){{/if}})
       {{/commit-list}}
 

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -9,29 +9,29 @@ body:
   - type: markdown
     attributes:
       value: "
-Thanks for taking the time to fill out this bug report!
+        Thanks for taking the time to fill out this bug report!
 
 
-Before submitting, make sure you search in the [issue list](https://github.com/BlueBrain/dir-content-diff/issues) that a similar issue was not already reported.
-If it is not the case, please read the following guidelines.
+        Before submitting, make sure you search in the [issue list](https://github.com/BlueBrain/dir-content-diff/issues) that a similar issue was not already reported.
+        If it is not the case, please read the following guidelines.
 
-### GUIDELINES FOR REPORTING BUGS
+        ### GUIDELINES FOR REPORTING BUGS
 
-Bug reports that are not properly formulated and formatted or without enough details can be very hard for us to understand and fix.
-In order to ensure we can help you fixing your bug, please follow these guidelines.
+        Bug reports that are not properly formulated and formatted or without enough details can be very hard for us to understand and fix.
+        In order to ensure we can help you fixing your bug, please follow these guidelines.
 
 
-Your reports must include the following features:
+        Your reports must include the following features:
 
-1. **succinct description** of the problem - typically a line or two at most.
+        1. **succinct description** of the problem - typically a line or two at most.
 
-2. **succinct, dependency-free code** which reproduces the problem, otherwise known as a [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/mcve) example.
-  IF YOU DO NOT HAVE A COMPLETE, RUNNABLE TEST CASE WRITTEN DIRECTLY IN THE TEXTAREA BELOW, YOUR ISSUE MAY BE CLOSED.
+        2. **succinct, dependency-free code** which reproduces the problem, otherwise known as a [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/mcve) example.
+          IF YOU DO NOT HAVE A COMPLETE, RUNNABLE TEST CASE WRITTEN DIRECTLY IN THE TEXTAREA BELOW, YOUR ISSUE MAY BE CLOSED.
 
-3. **complete stack traces for all errors** - please avoid screenshots, use formatted text inside issues.
+        3. **complete stack traces for all errors** - please avoid screenshots, use formatted text inside issues.
 
-4. other relevant things as applicable: **dependencies**, **comparative performance timings** for performance issues, etc.
-"
+        4. other relevant things as applicable: **dependencies**, **comparative performance timings** for performance issues, etc.
+      "
 
   - type: textarea
     attributes:
@@ -45,8 +45,8 @@ Your reports must include the following features:
     attributes:
       label: Optional link from https://dir-content-diff.readthedocs.io which documents the behavior that is expected
       description: "
-Please make sure the behavior you are seeing is definitely in contradiction to what's documented as the correct behavior.
-"
+        Please make sure the behavior you are seeing is definitely in contradiction to what's documented as the correct behavior.
+      "
     validations:
       required: false
 
@@ -54,7 +54,8 @@ Please make sure the behavior you are seeing is definitely in contradiction to w
     attributes:
       label: To Reproduce
       description: "
-Provide your [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/mcve) example here."
+        Provide your [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/mcve) example here.
+      "
       placeholder: "# Insert code here (text area already python formatted)"
       render: Python
     validations:
@@ -64,9 +65,9 @@ Provide your [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/
     attributes:
       label: Error
       description: "
-Provide the complete text of any errors received **including the complete stack trace**.
-If the message is a warning, run your program with the ``-Werror`` flag: ``python -Werror myprogram.py``
-"
+        Provide the complete text of any errors received **including the complete stack trace**.
+        If the message is a warning, run your program with the ``-Werror`` flag: ``python -Werror myprogram.py``
+      "
       placeholder: "# Copy the complete stack trace and error message here (text area already formatted for Python backtrace)"
       render: Python traceback
     validations:

dir_content_diff-1.15.1/.github/ISSUE_TEMPLATE/feature_request.yaml

@@ -0,0 +1,56 @@
+# docs https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms
+# https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema
+
+name: Request a new use case
+description: Support for new features
+labels: [enhancement]
+title: "[Feature request] "
+body:
+  - type: markdown
+    attributes:
+      value: "
+        Thanks for taking the time to fill out this feature request!
+
+
+        Before submitting, make sure the feature does not already exist in the [documentation](https://dir-content-diff.readthedocs.io) and that you searched in the [issue list](https://github.com/BlueBrain/dir-content-diff/issues) that a similar feature request has not already been reported.
+        If it is not the case, please read the following guidelines.
+
+        ### GUIDELINES FOR REQUESTING HELP
+
+        Feature requests that are not properly formulated and formatted or without enough details can be very hard for us to understand.
+        In order to ensure we can help you, please follow these guidelines.
+
+
+        Your requests must include the following features:
+
+        1. **succinct description** of the feature - typically a line or two at most to describe what the new feature would do.
+
+        2. **succinct, dependency-free code** which shows how you would like to use this feature, otherwise known as a [Minimal, Complete, and Verifiable](https://stackoverflow.com/help/mcve) example.
+
+        3. Why do you need this feature? What would be the use cases?
+      "
+
+  - type: textarea
+    attributes:
+      label: Describe the feature
+      description: A clear and concise description of what the feature would consist in.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Example Use
+      description: Provide a clear example of what the usage of this feature would look like.
+    validations:
+      required: true
+
+  - type: textarea
+    attributes:
+      label: Use cases
+      description: Add as much information as possible about the use cases here.
+    validations:
+      required: true
+
+  - type: markdown
+    attributes:
+      value: "### Thanks! Have a nice day!"

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/ISSUE_TEMPLATE/how_to_use.yaml

@@ -9,31 +9,31 @@ body:
   - type: markdown
     attributes:
       value: "
-Thanks for using this package and taking the time to fill out this help request!
+        Thanks for using this package and taking the time to fill out this help request!
 
 
-Before submitting, make sure you read the [documentation](https://dir-content-diff.readthedocs.io) carefully.
-If you still have a question, you should search in the [issue list](https://github.com/BlueBrain/dir-content-diff/issues) that a similar issue has not already been reported, you might find your answer there.
-If it is not the case, please read the following guidelines.
+        Before submitting, make sure you read the [documentation](https://dir-content-diff.readthedocs.io) carefully.
+        If you still have a question, you should search in the [issue list](https://github.com/BlueBrain/dir-content-diff/issues) that a similar issue has not already been reported, you might find your answer there.
+        If it is not the case, please read the following guidelines.
 
-### GUIDELINES FOR REQUESTING HELP
+        ### GUIDELINES FOR REQUESTING HELP
 
-Questions that are not properly formulated and formatted or without enough details can be very hard for us to understand.
-In order to ensure we can help you, please follow these guidelines.
+        Questions that are not properly formulated and formatted or without enough details can be very hard for us to understand.
+        In order to ensure we can help you, please follow these guidelines.
 
 
-Your requests must include the following features:
+        Your requests must include the following features:
 
-1. **succinct description** of the problem - typically a line or two at most to describe what you want to achieve.
+        1. **succinct description** of the problem - typically a line or two at most to describe what you want to achieve.
 
-2. **succinct, dependency-free code** which shows what you tried to do, otherwise known as a [Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve).
+        2. **succinct, dependency-free code** which shows what you tried to do, otherwise known as a [Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve).
 
-3. **expected results**
+        3. **expected results**
 
-4. **complete stack traces for all errors** if you have any - please avoid screenshots, use formatted text inside issues.
+        4. **complete stack traces for all errors** if you have any - please avoid screenshots, use formatted text inside issues.
 
-5. other relevant things: **dependencies**, **operating system**, **comparative performance timings** for performance issues.
-"
+        5. other relevant things: **dependencies**, **operating system**, **comparative performance timings** for performance issues.
+      "
 
   - type: textarea
     attributes:
@@ -46,7 +46,8 @@ Your requests must include the following features:
     attributes:
       label: Show what you tried to do.
       description: "
-Provide your [Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve) here."
+        Provide your [Minimal, Complete, and Verifiable Example](https://stackoverflow.com/help/mcve) here.
+      "
       placeholder: "# Insert code here (text area already python formatted)"
       render: Python
     validations:
@@ -63,9 +64,9 @@ Provide your [Minimal, Complete, and Verifiable Example](https://stackoverflow.c
     attributes:
       label: Error
       description: "
-If you are facing an arror, provide the complete text of any errors received **including the complete stack trace**.
-If the message is a warning, run your program with the ``-Werror`` flag: ``python -Werror myprogram.py``
-"
+        If you are facing an arror, provide the complete text of any errors received **including the complete stack trace**.
+        If the message is a warning, run your program with the ``-Werror`` flag: ``python -Werror myprogram.py``
+      "
       placeholder: "# Copy the complete stack trace and error message here (text area already formatted for Python backtrace)"
       render: Python traceback
     validations:

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/pull_request_template.md

@@ -1,5 +1,5 @@
 <!-- Provide a general summary of your proposed changes in the Title field above -->
-<!-- The title should have the following form: 'Type: Subject' with 'type' in [Build,Chore,CI,Reprecate,Docs,Feat,Fix,Perf,Refactor,Revert,Style,Test] -->
+<!-- The title should have the following form: 'Type: Subject' with 'type' in [Build,Chore,CI,Deprecate,Docs,Feat,Fix,Perf,Refactor,Revert,Style,Test] -->
 
 ### Description
 <!-- Describe your changes in detail and the reasons of these changes -->

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/workflows/commitlint.yml

@@ -11,11 +11,10 @@ jobs:
     env:
       PR_TITLE: ${{ github.event.pull_request.title }}
     steps:
-      - uses: actions/checkout@v6
-      - uses: actions/setup-node@v6
+      - uses: actions/checkout@v7
+      - uses: actions/setup-node@v7
         with:
           node-version: '20'
       - run: npm install -g --force commitlint @commitlint/cli commitlint-plugin-cleanfeet
-      - run: npm install conventional-changelog-conventionalcommits
       - run: touch .git/COMMIT_EDITMSG
       - run: echo "$PR_TITLE" | commitlint

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/workflows/publish-sdist.yml

@@ -9,10 +9,12 @@ jobs:
   build-n-publish:
     name: Build and publish on PyPI
     runs-on: ubuntu-latest
+    permissions:
+      id-token: write
     steps:
-      - uses: actions/checkout@v6
+      - uses: actions/checkout@v7
       - name: Set up Python 3.10
-        uses: actions/setup-python@v6
+        uses: actions/setup-python@v7
         with:
           python-version: "3.10"
       - name: Build a wheel and a source tarball
@@ -21,5 +23,3 @@ jobs:
           python -m build -o dist
       - name: Publish distribution package to PyPI
         uses: pypa/gh-action-pypi-publish@release/v1
-        with:
-          password: ${{ secrets.PYPI_API_TOKEN }}

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.github/workflows/run-tox.yml

@@ -12,21 +12,21 @@ on:
 jobs:
   build:
 
-    runs-on: ubuntu-latest
+    runs-on: ubuntu-24.04
     strategy:
       matrix:
-        python-version: ["3.9", "3.10", "3.11", "3.12"]
+        python-version: ["3.10", "3.11", "3.12"]
         min_versions: ["min_versions", "latest_versions"]
         exclude:
           - min_versions: "min_versions"
         include:
-          - python-version: "3.9"
+          - python-version: "3.10"
             min_versions: "min_versions"
 
     steps:
-    - uses: actions/checkout@v6
+    - uses: actions/checkout@v7
     - name: Set up Python ${{ matrix.python-version }}
-      uses: actions/setup-python@v6
+      uses: actions/setup-python@v7
       with:
         python-version: ${{ matrix.python-version }}
     - name: Get current month
@@ -35,13 +35,13 @@ jobs:
     - name: Install APT Packages
       run: |
         sudo apt-get install -y poppler-utils imagemagick
-    - name: Cache tox and precommit environments
-      uses: actions/cache@v5
+    - name: Cache tox and prek environments
+      uses: actions/cache@v6
       with:
         path: |
           .tox
-          ~/.cache/pre-commit
-        key: ${{ runner.os }}-${{ matrix.python-version }}-${{ steps.date.outputs.date }}-${{ hashFiles('setup.py') }}-${{ hashFiles('.pre-commit-config.yaml') }}
+          ~/.cache/prek
+        key: ${{ runner.os }}-${{ matrix.python-version }}-${{ steps.date.outputs.date }}-${{ hashFiles('setup.py', 'pyproject.toml', 'tox.ini', 'dir_content_diff/comparators/dependencies.json', '.pre-commit-config.yaml') }}
     - name: Clear results in tox environments
       run: |
         rm -rf .tox/*/tmp
@@ -49,13 +49,13 @@ jobs:
       if: ${{ matrix.min_versions == 'latest_versions' }}
       run: |
         python -m pip install --upgrade pip setuptools
-        pip install tox-gh-actions
+        pip install tox-uv tox-gh-actions
         tox
     - name: Run tox with min versions
       if: ${{ matrix.min_versions == 'min_versions' }}
       run: |
         python -m pip install --upgrade pip setuptools
-        pip install tox
+        pip install tox-uv
         tox run -e min_versions
     - name: JUnit Report Action
       uses: mikepenz/action-junit-report@v6
@@ -63,7 +63,7 @@ jobs:
       with:
         report_paths: 'reports/pytest-*.xml'
     - name: Upload to codecov
-      uses: codecov/codecov-action@v5
+      uses: codecov/codecov-action@v7
       with:
         fail_ci_if_error: false
         directory: ./reports
@@ -81,11 +81,12 @@ jobs:
       env:
         CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
     - name: Upload test artifacts
-      uses: actions/upload-artifact@v6
+      uses: actions/upload-artifact@v7
       if: always()
       with:
         name: tests-${{ matrix.python-version }}-${{ matrix.min_versions }}
         retention-days: 4
+        include-hidden-files: true
         path: |
           .tox/py*/tmp
           docs/build

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.gitignore

@@ -41,3 +41,9 @@ examples/.ipynb_checkpoints
 # Node
 node_modules
 package-lock.json
+
+# worktrees
+worktrees
+
+# graft's local graph cache — regenerable, not committed (run `graft build`).
+/graft/

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/.pre-commit-config.yaml

@@ -1,12 +1,16 @@
+default_install_hook_types:
+  - pre-commit
+  - commit-msg
+
 repos:
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: v0.7.0
+    rev: v0.15.19
     hooks:
       - id: ruff
         args: ["--fix", "--exit-non-zero-on-fix"]
       - id: ruff-format
   - repo: https://github.com/pre-commit/pre-commit-hooks
-    rev: v5.0.0
+    rev: v6.0.0
     hooks:
       - id: check-added-large-files
       - id: check-case-conflict
@@ -17,18 +21,17 @@ repos:
       - id: end-of-file-fixer
       - id: trailing-whitespace
   - repo: https://github.com/alessandrojcm/commitlint-pre-commit-hook
-    rev: v9.18.0
+    rev: v9.26.0
     hooks:
         - id: commitlint
           stages:
             - commit-msg
-          additional_dependencies: ['conventional-changelog-conventionalcommits']
   - repo: https://github.com/pycqa/isort
-    rev: 5.13.2
+    rev: 9.0.0a3
     hooks:
       - id: isort
   - repo: https://github.com/codespell-project/codespell
-    rev: v2.3.0
+    rev: v2.4.2
     hooks:
       - id: codespell
         args: ["-x", ".codespellignorelines"]
@@ -38,12 +41,12 @@ repos:
       - id: pydocstyle
         additional_dependencies: ["tomli"]
   - repo: https://github.com/PyCQA/flake8
-    rev: 7.1.1
+    rev: 7.3.0
     hooks:
       - id: flake8
         additional_dependencies: ['flake8-pyproject']
   - repo: https://github.com/arkinmodi/add-license-header
-    rev: v2.2.0
+    rev: v2.4.1
     hooks:
       - id: add-license-header
         args:

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/CHANGELOG.md

@@ -1,5 +1,30 @@
 # Changelog
 
+## [0.15.1](https://github.com/BlueBrain/dir-content-diff/compare/1.15.0..0.15.1)
+
+> 12 November 2026
+
+### CI Improvements
+
+- Fix publish job (Adrien Berchet - [#114](https://github.com/BlueBrain/dir-content-diff/pull/114))
+
+## [1.15.0](https://github.com/BlueBrain/dir-content-diff/compare/1.14.1..1.15.0)
+
+> 12 November 2026
+
+### Build
+
+- Update dependencies (Adrien Berchet - [#111](https://github.com/BlueBrain/dir-content-diff/pull/111))
+- Deprecate Python < 3.10 (dependabot[bot] - [#105](https://github.com/BlueBrain/dir-content-diff/pull/105))
+
+### New Features
+
+- Exit with code 1 when differences are found (Adrien Berchet - [#112](https://github.com/BlueBrain/dir-content-diff/pull/112))
+
+### Refactoring and Updates
+
+- Use DeepDiff instead of DictDiffer (Adrien Berchet - [#106](https://github.com/BlueBrain/dir-content-diff/pull/106))
+
 ## [1.14.1](https://github.com/BlueBrain/dir-content-diff/compare/1.14.0..1.14.1)
 
 > 15 January 2026
@@ -157,7 +182,7 @@
 
 - Cast exception args to str before joining them (Adrien Berchet - [#35](https://github.com/BlueBrain/dir-content-diff/pull/35))
 
-### Changes to Test Assests
+### Changes to Test Assets
 
 - Fix for Pandas>=2 (Adrien Berchet - [#33](https://github.com/BlueBrain/dir-content-diff/pull/33))
 

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/CONTRIBUTING.md

@@ -59,7 +59,7 @@ When you wish to contribute to the code base, please consider the following guid
   or
 
   ```shell
-  tox run -e py39,lint,docs,check-packaging
+  tox run -e py310,lint,docs,check-packaging
   ```
 
 * Commit your changes using a descriptive commit message.

{dir_content_diff-1.14.1/dir_content_diff.egg-info → dir_content_diff-1.15.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: dir-content-diff
-Version: 1.14.1
+Version: 1.15.1
 Summary: Simple tool to compare directory contents.
 Author: Blue Brain Project, EPFL
 License: Apache License 2.0
@@ -12,18 +12,17 @@ Classifier: Intended Audience :: Developers
 Classifier: License :: OSI Approved :: Apache Software License
 Classifier: Programming Language :: Python
 Classifier: Programming Language :: Python :: 3
-Classifier: Programming Language :: Python :: 3.9
 Classifier: Programming Language :: Python :: 3.10
 Classifier: Programming Language :: Python :: 3.11
 Classifier: Programming Language :: Python :: 3.12
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
-Requires-Python: >=3.9
+Requires-Python: >=3.10
 Description-Content-Type: text/markdown
 License-File: LICENSE.txt
 License-File: AUTHORS.md
 Requires-Dist: attrs>=21.3.0
 Requires-Dist: click>=8
-Requires-Dist: dictdiffer>=0.8
+Requires-Dist: deepdiff>=8.6
 Requires-Dist: dicttoxml>=1.7.12
 Requires-Dist: diff_pdf_visually>=1.7
 Requires-Dist: jsonpath-ng>=1.5
@@ -36,14 +35,14 @@ Requires-Dist: tables>=3.7; extra == "all-comparators"
 Requires-Dist: morphio>=3.3.6; extra == "all-comparators"
 Requires-Dist: morph_tool>=2.9; extra == "all-comparators"
 Requires-Dist: voxcell>=3.1.1; extra == "all-comparators"
-Requires-Dist: pynrrd<1.1,>=0.4; extra == "all-comparators"
+Requires-Dist: pynrrd>=0.4; extra == "all-comparators"
 Provides-Extra: docs
 Requires-Dist: myst_parser; extra == "docs"
 Requires-Dist: sphinx; extra == "docs"
 Requires-Dist: furo; extra == "docs"
 Provides-Extra: test
 Requires-Dist: dicttoxml>=1.7.16; extra == "test"
-Requires-Dist: matplotlib>=3.4; extra == "test"
+Requires-Dist: matplotlib<3.11,>=3.4; extra == "test"
 Requires-Dist: rst2pdf>=0.99; extra == "test"
 Requires-Dist: pandas>=1.4; extra == "test"
 Requires-Dist: pytest>=6.2; extra == "test"
@@ -60,7 +59,7 @@ Requires-Dist: morphio>=3.3.6; extra == "morphio"
 Requires-Dist: morph_tool>=2.9; extra == "morphio"
 Provides-Extra: voxcell
 Requires-Dist: voxcell>=3.1.1; extra == "voxcell"
-Requires-Dist: pynrrd<1.1,>=0.4; extra == "voxcell"
+Requires-Dist: pynrrd>=0.4; extra == "voxcell"
 Dynamic: license-file
 Dynamic: provides-extra
 
@@ -180,9 +179,9 @@ The previous code will output the following dictionary:
 {
     'file_1.c': (
         'The files \'reference_dir/file_1.c\' and \'compared_dir/file_1.c\' are different:\n'
-        'Added the value(s) \'{"2": 0}\' in the \'[b]\' key.\n'
-        'Changed the value of \'[a]\' from 1 to 2.\n'
-        'Changed the value of \'[b][0]\' from 1 to 10.'
+        'Added value at [\'b\'][2]: 0.\n'
+        'Changed value at [\'a\']: 1 -> 2.\n'
+        'Changed value at [\'b\'][0]: 1 -> 10.'
     )
 }
 ```
@@ -202,9 +201,9 @@ Which will output the following ``AssertionError``:
 
 ```bash
 AssertionError: The files 'reference_dir/file_1.c' and 'compared_dir/file_1.c' are different:
-Added the value(s) '{"2": 0}' in the '[b]' key.
-Changed the value of '[a]' from 1 to 2.
-Changed the value of '[b][0]' from 1 to 10.
+Added value at ['b'][2]: 0.
+Changed value at ['a']: 1 -> 2.
+Changed value at ['b'][0]: 1 -> 10.
 ```
 
 #### Advanced Configuration Options
@@ -235,6 +234,21 @@ dir_content_diff.assert_equal_trees(
 )
 ```
 
+Dictionary-based comparators such as JSON, YAML, XML and INI use keyword arguments for
+their comparison options. The project-specific `tolerance` and `absolute_tolerance`
+arguments control numeric comparisons. Useful DeepDiff options can also be passed as
+keywords, for example `exclude_paths`, `exclude_regex_paths`, `include_paths`,
+`ignore_order`, `ignore_string_case` and `max_diffs`.
+
+```python
+specific_args = {
+    "sub_dir_1/sub_file_1.a": {
+        "exclude_paths": {"root['metadata']['timestamp']"},
+        "ignore_order": True,
+    }
+}
+```
+
 Each comparator has different arguments that are detailed in the documentation.
 
 ##### File-specific Comparators

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/README.md

@@ -114,9 +114,9 @@ The previous code will output the following dictionary:
 {
     'file_1.c': (
         'The files \'reference_dir/file_1.c\' and \'compared_dir/file_1.c\' are different:\n'
-        'Added the value(s) \'{"2": 0}\' in the \'[b]\' key.\n'
-        'Changed the value of \'[a]\' from 1 to 2.\n'
-        'Changed the value of \'[b][0]\' from 1 to 10.'
+        'Added value at [\'b\'][2]: 0.\n'
+        'Changed value at [\'a\']: 1 -> 2.\n'
+        'Changed value at [\'b\'][0]: 1 -> 10.'
     )
 }
 ```
@@ -136,9 +136,9 @@ Which will output the following ``AssertionError``:
 
 ```bash
 AssertionError: The files 'reference_dir/file_1.c' and 'compared_dir/file_1.c' are different:
-Added the value(s) '{"2": 0}' in the '[b]' key.
-Changed the value of '[a]' from 1 to 2.
-Changed the value of '[b][0]' from 1 to 10.
+Added value at ['b'][2]: 0.
+Changed value at ['a']: 1 -> 2.
+Changed value at ['b'][0]: 1 -> 10.
 ```
 
 #### Advanced Configuration Options
@@ -169,6 +169,21 @@ dir_content_diff.assert_equal_trees(
 )
 ```
 
+Dictionary-based comparators such as JSON, YAML, XML and INI use keyword arguments for
+their comparison options. The project-specific `tolerance` and `absolute_tolerance`
+arguments control numeric comparisons. Useful DeepDiff options can also be passed as
+keywords, for example `exclude_paths`, `exclude_regex_paths`, `include_paths`,
+`ignore_order`, `ignore_string_case` and `max_diffs`.
+
+```python
+specific_args = {
+    "sub_dir_1/sub_file_1.a": {
+        "exclude_paths": {"root['metadata']['timestamp']"},
+        "ignore_order": True,
+    }
+}
+```
+
 Each comparator has different arguments that are detailed in the documentation.
 
 ##### File-specific Comparators

{dir_content_diff-1.14.1 → dir_content_diff-1.15.1}/commitlint.config.js

@@ -1,5 +1,15 @@
 module.exports = {
-	parserPreset: 'conventional-changelog-conventionalcommits',
+	parserPreset: {
+		parserOpts: {
+			headerPattern: /^(\w*)(?:\((.*)\))?!?: (.*)$/,
+			breakingHeaderPattern: /^(\w*)(?:\((.*)\))?!: (.*)$/,
+			headerCorrespondence: ['type', 'scope', 'subject'],
+			noteKeywords: ['BREAKING CHANGE', 'BREAKING-CHANGE'],
+			revertPattern: /^(?:Revert|revert:)\s"?([\s\S]+?)"?\s*This reverts commit (\w*)\./i,
+			revertCorrespondence: ['header', 'hash'],
+			issuePrefixes: ['#'],
+		},
+	},
 	rules: {
 		'body-leading-blank': [1, 'always'],
 		'body-max-line-length': [2, 'always', 100],