Bånderapp:genre:song:add
Assign a genre to a song. The command does what POST /api/genres/{slug}/songs does in the admin API, through the same port.
Quick start
make exec cmd="php bin/console app:genre:song:add rock aB3dE5fG7hJ9kL1mN3pQr"
In a script that reads only the exit code:
make exec cmd="php bin/console app:genre:song:add rock aB3dE5fG7hJ9kL1mN3pQr --json"
Arguments
| Argument | Required | Description |
|---|---|---|
slug |
Yes | The genre slug |
song-id |
Yes | The song public ID |
Options
| Option | Description |
|---|---|
--json |
Print nothing on success, as the admin API answers 204 No Content; the exit code reports the outcome |
Details
Assigning a genre the song already has succeeds and leaves one link, so a retry is harmless. A song public ID that names no song fails with Song not found., which the API answers with 404. To undo the assignment, use app:genre:song:remove.
With --json the command prints nothing on success, because the API answers 204 No Content; read the outcome from the exit code. Errors still go to stderr.
Exit codes
| Code | Meaning |
|---|---|
| 0 | The song has the genre |
| 1 | No genre has the slug, no song has the song ID, or another error occurred; the message says why |
| 2 | The song ID is not a public ID |