.csv

[marcderbauer]

Add saving .csv the outcome as a .csv file. Will still need to think this through, but probably want each row to be a song and each column as one of the song attributes.

Open Questions

• how does this work for querying artists? Should there be one artist.csv?
• how does this work for querying playlists?
• where should the lyrics be saved? In the .csv? Probably, right?

—

Created via Raycast

[marcderbauer]

Should be the same as when saving .json files. Same folder structure, same way files are saved:

• artist/album/album.csv
• Keep lyrics and statistics together
• Use iter() method to serialise. See more here: https://dev.to/htv2012/how-to-write-a-class-object-to-csv-5be1

[marcderbauer]

Could maybe make part where it checks for a folder and creates one if necessary into a method. Maybe as part of the Music class

[marcderbauer]

Implemented this as a classmethod for now. Would be cool to have it as a regular (object) method, but not possible without changing nomenclature.

self.name currently refers to different things depending on if it's an album or a song... Would need to turn it into something like self.songname, self.albumname, self.artistname, self.playlistname,...

[marcderbauer]

Changed self.name to be more consistent (now self.song_name, self.album_name,...) Save song is correctly implemented as well now and can overwrite existing songs if necessary. This works both for .csv and for .json.

Added methods for reading albums from .csv and .json

Added ASCII headers to find things easier

Multipool error handling (quite simple for now, just writes to a file once, but errors aren't that frequent anyway).

--overwrite works for songs, still needs to be checked for albums and artists.

Genius album functionality removed. Artists having different songs with the same name is too much of an edge case to support.