view release on metacpan or  search on metacpan

CHANGES  view on Meta::CPAN

    - Added single test report get API. This works for new-style reports
      only. We will be migrating old-style reports to the new-style
      format soon. Old-style reports will maintain their former ID, so
      everything should work fine.

    [Fixed]

    - Upgraded Mojolicious::Plugin::OpenAPI to 1.13 to fix deprecations
      due to Mojo::File
    - Fixed API website links to point to /v3 API endpointes
    - Fixed test report post to use new schema with auto-serialization.
      This makes our database more consistent.

0.007     2017-05-12 10:35:47+02:00 Europe/Paris

    [Added]

    - Added v3 API spec with posting of incoming test reports. Thanks
      @garu! [Github #5]

CHANGES  view on Meta::CPAN

0.004     2016-12-17 18:28:28-06:00 America/Chicago

    [Added]

    - /uploads API for querying the CPAN uploads information table. See
      http://api.cpantesters.org/docs/?url=/v1#!/default/uploads for
      details.

    - Upload feeds to get push notifications of new CPAN uploads via
      WebSockets. Subscribe to any /uploads endpoint to get a feed of
      new information from that endpoint.

0.003     2016-11-26 21:10:39-06:00 America/Chicago

    [Added]

    - Introductory information on the root
    - API documentation using Alien::SwaggerUI

0.002     2016-11-20 19:15:28-06:00 America/Chicago

CONTRIBUTING.md  view on Meta::CPAN

Any files that are not runnable code but must still be available to the
code are stored in `share/`. This includes default config files, default
content, informational files, read-only databases, and other such. This
project uses [File::Share](http://metacpan.com/pod/File::Share) to
locate these files at run-time.

##### `share/api.json`

This is the [OpenAPI specification](http://openapis.org) for the CPAN
Testers API. This JSON document documents each API endpoint, the input
it can receive, the output it will send, and any error conditions that
might occur. This API documentation is then displayed [using
SwaggerUI](http://swagger.io/swagger-ui) (via
[Alien::SwaggerUI](http://metacpan.org/pod/Alien::SwaggerUI)) at
<http://api.cpantesters.org>.

Every new API endpoint must be started and documented here. This
document is used by
[Mojolicious::Plugin::OpenAPI](http://metacpan.org/pod/Mojolicious::Plugin::OpenAPI)
to generate the Mojolicious routes and validate the input and output
automatically. Each route should have an `x-mojo-to` key to link it to
a `controller` (class) and `action` (method). It should also have an
`operationId` that is globally unique for all API files.

##### `share/templates`

This is where Mojolicious templates should go. The templates are located