Backup_Repos/beets
1
0
Fork 0
mirror of https://github.com/beetbox/beets.git synced 2026-01-06 07:53:40 +01:00
Code Issues Projects Releases Wiki Activity

[doc/reference/config] Re-write explanation for 'overwrite_null'

Browse source 
See: <https://github.com/beetbox/beets/pull/5373#discussion_r1702848037>
This commit is contained in:
Arav K. 2024-09-08 14:14:37 +02:00 committed by arya dradjica
parent c668dfae71
commit 0a985fdfb4
1 changed files with 5 additions and 5 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

10
docs/reference/config.rst
View file

@ -281,11 +281,11 @@ That is, if this option is turned on, then ``year`` will always equal
overwrite_null
~~~~~~~~~~~~~~
In some situations, data for a particular field is not available, and it ends up being
set to an empty value (an empty string). To allow such fields to be overwritten once
the appropriate data does become available (e.g. by a re-import or a manual update),
the name of the metadata field can be added to the list `album` (for albums) or `track`
(for tracks). For example::
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"]