Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-rest
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & 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
  • ensembl-gh-mirror
  • ensembl-rest
  • Merge requests
  • !34

Closed
Created Jan 15, 2015 by Marek Szuba@mks
  • Report abuse
Report abuse

Updated documentation to show where paramaters go

  • Overview 2
  • Commits 1
  • Changes 1

Created by: Relequestual

It's not clear in the documentation that the paramaters are used in different ways. The required paramater is part of the URL, while the optional paramaters must be part of the message root object. I found this out myself, as I followed the previous example of a single vep query (where the optional paramaters were appened as a query string).

I don't know if I quite got the format your documentation right. Please let me know / fix it if not.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: github/fork/Relequestual/patch-1