Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Document overwrite_null #5373

Merged
merged 2 commits into from
Sep 12, 2024
Merged

Document overwrite_null #5373

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
eff935e
Document 'overwrite_null'
Jul 31, 2024
3310bc1
[doc/reference/config] Re-write explanation for 'overwrite_null'
Sep 8, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 15 additions & 0 deletions docs/reference/config.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -276,6 +276,21 @@ Either ``yes`` or ``no``, indicating whether matched albums should have their
That is, if this option is turned on, then ``year`` will always equal
``original_year`` and so on. Default: ``no``.

.. _overwrite_null:

overwrite_null
snejus marked this conversation as resolved.
Show resolved Hide resolved
~~~~~~~~~~~~~~

This confusingly-named option indicates which fields have meaningful `null` values. If
an album or track field is in the corresponding list, then an existing value for this
field in an item in the database can be overwritten with `null`. By default, however,
`null` is interpreted as information about the field being unavailable, so it would not
overwrite existing values. For example::

overwrite_null:
album: ["albumid"]
track: ["title", "date"]

.. _artist_credit:

artist_credit
Expand Down