feat: new MetaAlbum and MetaTrack classes

These classes are used to represent albums and tracks containing only metadata i.e. they do not exist in the filesystem or database. This is useful when describing an album or track from an online source e.g. musicbrainz.
MoeMusic · Oct 30, 2022 · e496e7c · e496e7c
1 parent 32cda47
commit e496e7c
Show file tree

Hide file tree

Showing 15 changed files with 807 additions and 407 deletions.
diff --git a/docs/developers/api/core.rst b/docs/developers/api/core.rst
@@ -27,7 +27,7 @@ Library
 
 .. automodule:: moe.library
    :members:
-   :exclude-members: cache_ok, path, year, genre, original_year
+   :exclude-members: cache_ok, path, year, catalog_num, genre, original_year
    :show-inheritance:
 
 

diff --git a/docs/developers/contributing.rst b/docs/developers/contributing.rst
@@ -133,9 +133,9 @@ New Field Checklist
 If adding a new field to Moe, the following checklist can help ensure you cover all your bases:
 
 #. Add the database column to the appropriate library class (``Album``, ``Extra``, or ``Track``).
-
+   * If the field represents metadata and does not deal with the filesystem, also add to the appropriate ``Meta`` class (``MetaAlbum`` or ``MetaTrack``).
    * If a multi-value field, add the non-plural equivalent property. See ``Track.genres`` and the accompanying single-value field, ``Track.genre`` for an example.
-   * Include documentation for the new field in the class docstring.
+   * Include documentation for the new field in the class docstring(s).
 
 #. Add to the item's ``fields`` method as necessary.
 #. Add code for reading the tag from a track file under ``Track.read_custom_tags``.