Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • funkwhale funkwhale
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 375
    • Issues 375
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 16
    • Merge requests 16
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • funkwhalefunkwhale
  • funkwhalefunkwhale
  • Issues
  • #573
Closed
Open
Issue created Oct 11, 2018 by Agate@agateMaintainer

Add "type" attribute in subsonic payload

This is used for some client apps for graceful degrading:

A few other Subsonic server variants identify themselves to client apps by adding an extra “type” property to the response, for example:
{
  "subsonic-response": {
    “type”: “funkwhale”,
    "status": "failed",
    "version": "1.16.0",
    "error": {
      "code": 40,
      "message": "Wrong username or password."
    }
  }
}

Doing so would allow the client app to adapt more gracefully to partially implemented APIs

This is suggested by one of the developper from the play:Sub app.

Edited Oct 11, 2018 by Agate
Assignee
Assign to
Time tracking