Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
C
Cygnus
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • Cygnus
  • Cygnus
  • Issues
  • #7

Closed
Open
Opened Oct 19, 2017 by Luke081515@LukeOwner

Get a uniform format for API-Urls

When formatting an API URL there are several ways at the moment, one is putting all the extra rubish in one line. That's not that readable, additionally phpcs freaks out when it sees that. So we need a good way to format all these URLs. What format do you prefer?

I prefer something like:

		$data = 'action=watch'
			. '&format=json'
			. '&unwatch=' . $unwatch
			. '&titles=' . urlencode($title)
			. '&token=' . urlencode($token)
			. '&assert=' . $this->assert
			. '&maxlag=' . $this->maxlag;

(From merge request 5)

Easy to read, but tends to get long.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Version 2.2
Milestone
Version 2.2
Assign milestone
Time tracking
None
Due date
None
Reference: Cygnus/Cygnus#7