Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.web
beat.web
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 54
    • Issues 54
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.webbeat.web
  • Issues
  • #193

Closed
Open
Opened Jun 01, 2015 by André Anjos@andre.anjos💬
  • Report abuse
  • New issue
Report abuse New issue

Use Swagger for ReSTful API

With the BEAT deliverables out of the way, it would be nice to think about a longer term documentation strategy for our web APIs. Now everything (please correct me if I'm wrong) uses Django's rest framework, it would be good to go for Swagger. It is, at least, the recommendation from that library: http://www.django-rest-framework.org/topics/documenting-your-api/

Assignee
Assign to
BEAT Tour
Milestone
BEAT Tour
Assign milestone
Time tracking
None
Due date
None
0
Labels
None
Assign labels
  • View project labels
Reference: beat/beat.web#193