2017 © Pedro Peláez
 

project apigility-raml-validator

Validate an Apgility implementation against a RAML specification

image

robertboloc/apigility-raml-validator

Validate an Apgility implementation against a RAML specification

  • Friday, March 31, 2017
  • by robertboloc
  • Repository
  • 1 Watchers
  • 3 Stars
  • 0 Installations
  • PHP
  • 0 Dependents
  • 0 Suggesters
  • 0 Forks
  • 0 Open issues
  • 7 Versions
  • 0 % Grown

The README.md

apigility-raml-validator

Build Status License, (*1)

This is a tool to help validate your Apigility implementation against a RAML specification. This way you can make sure the implementation matches the specification requirements., (*2)

In comparison with similar tools this application does not check the output of the api but the code structure directly., (*3)

Please note that this tool is in early stages of development., (*4)

Table of contents

Installation

composer require --dev "robertboloc/apigility-raml-validator"
chmod +x vendor/bin/apigility-raml-validator

Usage

vendor/bin/apigility-raml-validator [--help] [-s spec, --spec spec] [-p project, --project project]

Options

spec (-s | --spec)

Path to the RAML specification file, (*5)

target (-p | --project)

Path to the Apigility project containing the source code, (*6)

module (-m | --module)

Hint the name of the module in case it's different from the API name, (*7)

help (--help)

Display the usage message, (*8)

debug (--debug)

Enable debug messages when running the application, (*9)

Validation

This is the list of fields from the RAML specification currently being validated, (*10)

RAML Apigility
title Check a module matching title exists
version Check a version folder matching version exists
resource * Check a route has been defined for the resource
method Check a collection route implements the methods of a top resource

* only top level resources are detected for now, (*11)

Example

Highlighted in green are the lines of the RAML specification currently being validated against the implementation, (*12)

  #%RAML 1.0
+ title: Test
+ version: v1
- protocols: HTTPS
- mediaType: application/json
- baseUri: https://api.test.com/{version}
- description: My Test API

+ /foo:
+   get:
+     description: My test endpoint

+ /bar:
+   post:
+     description: Another test endpoint

The Versions

31/03 2017

dev-master

9999999-dev

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

31/03 2017

dev-feature-debug-mode

dev-feature-debug-mode

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

30/03 2017

dev-feature-documentation-check

dev-feature-documentation-check

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

29/03 2017

dev-feature-module-name-hint

dev-feature-module-name-hint

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

12/03 2017

dev-feature-tests

dev-feature-tests

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

10/03 2017

dev-feature-unit-testing

dev-feature-unit-testing

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires

 

The Development Requires

08/03 2017

dev-feature-endpoints

dev-feature-endpoints

Validate an Apgility implementation against a RAML specification

  Sources   Download

MIT

The Requires