Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
  • Sign in / Register
M
Manuscripts API
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • Manuscripts.app Public
  • Manuscripts API
  • Issues
  • #6

Closed
Open
Opened Dec 28, 2020 by Casey Ydenberg@CAYdenbergOwner

Inconsistency in returned scoped project token

The documentation for the authorization:scope endpoint says it will send responses in either application/json or text/plain format; however the default appears to be JSON.

Conversely, the documentation for /:containerType/:container/:scope endpoint says it will send only application/json responses; however in reality we get plain text responses (if no Accept header is sent).

It would be nice if these were at least consistent; to avoid breaking current implementations I think they should both be flexible based on the Accept header but should send plain text by default.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: mpapp-public/manuscripts-api#6