Summary
Multi-level (nested) playlists are expected to deduplicate their contents, but they currently don't. The flattened contents contain duplicate UUIDs.
Example
Playlist: https://alpha.infinidream.ai/playlist/d323733e-51a4-4ca7-a912-347087e90252
- 6300 total UUIDs in the resolved/flattened contents
- only 4500 unique UUIDs
- → ~1800 duplicates
Expected
When a playlist references other playlists (multi-level nesting), the resolved contents should be deduplicated so each UUID appears at most once.
Actual
Duplicates are present in the flattened output, presumably because the same dream/playlist is reachable via more than one nested branch and dedup isn't applied after flattening.
Notes
Reported from the client side. Worth confirming where dedup is expected to happen (at flatten/resolve time vs. at insert time) and whether the dedup should preserve first-occurrence ordering.
Summary
Multi-level (nested) playlists are expected to deduplicate their contents, but they currently don't. The flattened contents contain duplicate UUIDs.
Example
Playlist: https://alpha.infinidream.ai/playlist/d323733e-51a4-4ca7-a912-347087e90252
Expected
When a playlist references other playlists (multi-level nesting), the resolved contents should be deduplicated so each UUID appears at most once.
Actual
Duplicates are present in the flattened output, presumably because the same dream/playlist is reachable via more than one nested branch and dedup isn't applied after flattening.
Notes
Reported from the client side. Worth confirming where dedup is expected to happen (at flatten/resolve time vs. at insert time) and whether the dedup should preserve first-occurrence ordering.