onpositive


  • published version 0.0.6, 9 years ago
  • published version 0.0.9, 8 years ago
  • ###Disclaimer this readme is a partially joke, and contains a lot of hype. (It is written basing on the one in Saphire(framework which I used for inspiration)

    published version 0.0.10, 8 years ago
  • published version 0.0.7, 8 years ago
  • published version 0.0.1, 8 years ago
  • This repository contains a parser for RAML Type expressions grammar

    published version 0.0.9, 8 years ago
  • Interfaces used in RAML Type System

    published version 0.0.9, 8 years ago
  • Interfaces used in RAML Type System

    published version 0.0.21, 8 years ago
  • Nominal implementation of RAML types

    published version 0.0.10, 8 years ago
  • This is lighter version of RAML TypeSystem, dependencies are optimized, it is not capable to validate external types, and external types instances by design. Capability to validate types itself also might be removed in future.

    published version 0.0.22, 8 years ago
  • This repository contains typings on top of JSON serialization of [RAML1 JS Parser](https://github.com/raml-org/raml-js-parser-2/)

    published version 0.0.20, 8 years ago
  • RAML is a language for the definition of HTTP-based APIs that embody most or all of the principles of Representational State Transfer (REST)

    published version 0.0.22, 8 years ago
  • This repository contains lighweight API on top of JSON Serialization of RAML files. It uses interfaces described in [RAML Domain Model](https://github.com/petrochenko-pavel-a/raml-domain-model) to represent semantic of the RAML file.

    published version 0.0.24, 8 years ago
  • Different use cases require us to expose different representations(shapes) of same business entity.

    published version 0.0.22, 8 years ago
  • **Problem statement**: different use cases require us to expose different representations(shapes) of same business entity.

    published version 0.0.23, 8 years ago
  • RPC views is designed to represent RAML Api descriptions as collections of the functions. The goal of this representation is to allow client generators to be based on top of some unified mapping of HTTP interfaces into RPC calls, and as the result to si

    published version 0.0.25, 8 years ago
  • ``` The fundamental concept in any RESTful API is the resource. Resources can be grouped into collections. Each collection is homogeneous so that it contains only one type of resource, and unordered. Resources can also exist outside any collection.

    published version 0.0.24, 8 years ago