quintodrome/server/subsonic/responses/.snapshots/Responses AlbumWithSongsID3 without data should match .JSON

{
  "status": "ok",
  "version": "1.16.1",
  "type": "navidrome",
  "serverVersion": "v0.55.0",
  "openSubsonic": true,
  "album": {
    "id": "",
    "name": "",
    "songCount": 0,
    "duration": 0,
    "created": "0001-01-01T00:00:00Z"
  }
}
Fix marshaling for genres. 2023-11-21 16:09:12 -09:00			`{`
			`"status": "ok",`
chore(subsonic): update snapshot tests to use version 1.16.1 2025-03-27 18:50:22 -08:00			`"version": "1.16.1",`
Fix marshaling for genres. 2023-11-21 16:09:12 -09:00			`"type": "navidrome",`
chore(subsonic): update snapshot tests to use version 1.16.1 2025-03-27 18:50:22 -08:00			`"serverVersion": "v0.55.0",`
Fix marshaling for genres. 2023-11-21 16:09:12 -09:00			`"openSubsonic": true,`
			`"album": {`
			`"id": "",`
fix(subsonic): never omit duration for AlbumID3 (#5217) 2026-03-17 09:20:10 -08:00			`"name": "",`
fix(subsonic): mark AlbumID3 songCount and created as required The Subsonic API spec defines songCount and created as required attributes on AlbumID3, but they were tagged with omitempty in our response struct, allowing them to be silently dropped from responses (e.g. when songCount was 0). Created was also a time.Time, which compounded the omitempty behavior. Remove omitempty from both fields and change Created from time.Time to time.Time so they are always serialized, matching the spec contract that clients rely on. The buildAlbumID3 helper and its tests are updated for the non-pointer Created, and the AlbumWithSongsID3 snapshots are regenerated to include the now-always-present fields. 2026-05-22 13:42:17 -08:00			`"songCount": 0,`
			`"duration": 0,`
			`"created": "0001-01-01T00:00:00Z"`
Fix marshaling for genres. 2023-11-21 16:09:12 -09:00			`}`
			`}`