Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-5817

LTD Keeper: refactor REST routes; adopt JSON API conventions

    XMLWordPrintable

Details

    Description

      Right now resources are available on

      /products/
      /editions/
      /builds/
      

      routes, with editions and builds being known by their DB id number. It would be better to refer to these by their slug. To ensure uniqueness, this implies that builds and editions are sub-resources of products. I.e.

      /products/<prod_slug>
      /products/<prod_slug>/builds/<build_slug>
      /products/<prod_slug>/editions/<edition_slug>
      

      This ticket will complete this refactoring.

      Attachments

        Issue Links

          Activity

            Note that jsonapi.org would be something good to consider adopting.

            jsick Jonathan Sick added a comment - Note that jsonapi.org would be something good to consider adopting.

            Perhaps use the Marshmallow package to build json serializers to ensure consistent resource presentation.

            jsick Jonathan Sick added a comment - Perhaps use the Marshmallow package to build json serializers to ensure consistent resource presentation.
            tjenness Tim Jenness added a comment -

            jsick is this ticket still valid?

            tjenness Tim Jenness added a comment - jsick is this ticket still valid?

            This is still worth looking into.

            jsick Jonathan Sick added a comment - This is still worth looking into.

            People

              jsick Jonathan Sick
              jsick Jonathan Sick
              Jonathan Sick, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Jenkins

                  No builds found.