fix(editor): 'Deezer' autofill button is Deezer-only again (MusicBrainz has its own button)

Stufe B routed /api/meta/lookup through the combined resolver, so the editor's
'Deezer' button could silently return MusicBrainz data while the status said
'von Deezer'. The editor already has a dedicated 'MusicBrainz' button, so keep the
two explicit and honest: Deezer button = Deezer only. The combined
Deezer→MusicBrainz→clean resolver stays on the DOWNLOAD paths.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
HoneyandClaude Opus 4.8 committed 2026-08-12 16:53:25 +02:00
1 parent e61d57425e
commit 75dceba97b
1 file changed
+3 -1
+3 -1
View File
@@ -290,7 +290,9 @@ app.get('/api/meta/lookup', async (req, res) => {
const { artist, title } = req.query; const { artist, title } = req.query;
if (!artist || !title) return res.status(400).json({ error: 'artist and title required' }); if (!artist || !title) return res.status(400).json({ error: 'artist and title required' });
try { try {
const meta = await tm.lookupTrackMeta(artist, title); // Editor "Deezer" button = Deezer only (there is a separate "MusicBrainz" button). The combined
// Deezer→MusicBrainz→clean resolver (tm) is used by the DOWNLOAD paths, not this manual autofill.
const meta = await dz.lookupTrackMeta(artist, title);
if (!meta.album && !meta.genre && !meta.year) return res.json({ found: false }); if (!meta.album && !meta.genre && !meta.year) return res.json({ found: false });
res.json({ res.json({
found: true, found: true,