RAML Tools for .NETRAML Tools for .NET allows developers to easily integrate and consume APIs that exposes a RAML or OAS (swagger) definitions, or generate a new ASP.NET Web API implementation from scratch using a contract-first approach from a previously created RAML or OAS (swagger) definition... |
RAML Tools for .NET allows developers to easily integrate and consume APIs that exposes a RAML or OAS (swagger) definition, or generate a new ASP.NET Web API implementation from scratch using a contract-first approach from a previously created RAML or OAS (swagger) definition. See http://raml.org for information on RAML (RESTful API Modeling Language). Project home: https://github.com/mulesoft-labs/raml-dotnet-tools A number of sample projects can be found under the /samples directory in this repository. v 3.0.3 notes:
v 3.0.2 notes:
v 3.0.1 notes: API Console v6 v 3.0.0 notes: Note: This a pre release version that uses a new parser with support for OAS / OpenAPI and has many bug fixed from the previous version Main new features:
Release 2.1.2 notes:
Release 2.1.1 notes:
Release 2.1.0 notes:
Release 2.0.6 notes: - Adding Extract RAML for ASP .NET Core / MVC 6 - Include JSON schema parsing errors/warnings when adding a RAML contract - Generate API Client Code from a RAML definition in .NET core projects - Document how to update Generated Web API interface after RAML change - Update js parser to latest version - Fixed #111: String array properties not generated - Fixed #112: Route incorrectly generated - Fixed #121: Incorrect detection of "uses:" clause - Fixed #131: Invalid Generated RAML 1.0 - Fixed #133: Unable to edit RAML files when Adding a RAML reference - Fixed #134: Command line tools not picking up RAML include files in relative folders when referenced by a path in the command line Release 2.0.5 notes: - Fixed version number for the published VSIX file Release 2.0.4 notes: - Added possibility to allow customization of generated .Net primitive types - Added model classes generation - CLI Tool - Added support for DateTimeOffset - Fixed #93: optional properties - Fixed #94: integer types generating long type after last release - Fixed #102: Resource types generating long type after last release - Fixed #104: Two or more traits don't work if these traits contains responses - Fixed #105: Duplicate names in enums error For more information please click here. Release 2.0.3 notes: - Added possibility to customize output (folders / file names suffix) - Added support for Asp.Net Core - Added support for using C# long (System.Int64) in APIs - Fixed #83: Wrong use of Route instead in Web Api 2 gernated code - Fixed #84: Incorrect comments in Asp.Net 5 templates - Fixed #87: Traits applied at incorrect level - Fixed #88: Date type converted to object instead of DateTime - Fixed #90: Outdated dependencies in CLI Tools For more information please click here. Release 2.0.2 notes: - Fix issue with adding a new RAML contract Release 2.0.1 notes: - Fix issues with date / time data types in RAML 1.0 Release 2.0.0 notes: - Added support for RAML 1.0 specification * Note that this version of the tools will produce different model classes due to the new RAML type system. Release 1.4.1 notes: - Fixed #58: Collection of additionalProperties attached to wrong class - Fixed #59: JSON schema not being resolved - Fixed #61: Typo in generated comments Release 1.4.0 notes: - Added support for implementation of ASP.NET 5 based APIs - Added support for query objects in RAML Metadata output - Fixed #42: Support definition of root endpoint in RAML - Fixed #44: Patch HTTP verb upper-cased to be compatible with API Gateway - Fixed #46: Support for KeyValuePair collection - Fixed #49: Ensure query parameter format is compatible with API Gateway - Fixed #50: Include raw Location header value - Fixed #52: Add correct using statement to import generated Models - Fixed #54: Support multiple levels of hierarchy in properties Release 1.3.0 notes: - Transform JSON Schema validation attributes into Model DataAnnotations when scaffolding WebApi - Transform Model Data Annotations into JSON Schema validation attributes when reversing RAML from WebAPI implementation - RAML.Api.Core nuget package nows supports Core CLR - Portability issues resolved for cross-platform development Release 1.2.0 notes: - Added support for XML Schema in addition to JSON Schema - RAML.Api.Core is now portable, providing support for cross-platform app development (#14, #20) - RAML included in project now uses relative paths, simplifying collaboration (#19) - Added support for HTTP PATCH method in RAML and controllers (#32) - Support for JSON Schema version 4 additionalProperties collection (#6) - Fixed #23: Uri parameters metadata not inherited when nesting resources - Fixed #24: Importing RAML reference does not add .ref file to project - Fixed #28: Use request schema for PUT operation - Fixed #29: Support optional JSON elements with Nullable - Fixed #33: RAML metadata generator not correctly detecting concrete collection types - Fixed #34: Tools not working with bare arrays Release 1.1.1 notes: - Add support for generating async method signatures for API implementation - Show menu commands for Add RAML Reference and Add RAML Contract on API References and Contracts folders - Add a RAML properties editor dialog to allow updating generation parameters - Support for explicitly naming the client proxy class - Verified compatibility with Visual Studio 2015 - Fixed #11: Handle JSON object with the same name but different properties - Fixed #12: Separate JSON schema includes into their own subdirectory - Fixed #13: Support for nested JSON schemas - Fixed #15: Null reference when parsing bodyless traits - Fixed #16: Support for resolving project paths on any drive - Fixed #21: Handle properties that have no setters Release 1.1.0 notes: - Add RAML reference dialog now allows browsing Exchange for public and private APIs - Ability to reverse engineer a RAML definition from an existing WebApi (Enable RAML metadata output) - Compatibility with broader set of RAML definitions - Improved support for complex JSON schemas (fstab sample) - Support for enums in JSON schemas - Collection types now implement IList rather than ICollection - Sub-resources appear nested beneath parent resource to prevent conflicts - Force boolean values to lowercase during serialization to provide compatibility with ApiKit Release 1.0 has many improvements over 0.9: - Support for schema validation in the WebApi implementation - Allow T4 templates to be customized per project (and source controlled) - Types declared by schema property are respected in model generation - Support for complex schemas, including $ref properties (see example 2 from json-schema.org) - Improved ability to drive model generation using custom parameters in RAML - Collections are now implemented as IList rather than array types - RAML comments are now included in the implementation class to make code required more obvious - Sub-resources now appear nested beneath the parent resource in the model - The API client proxy name is now different to the enclosing namespace to improve intellisense - Bug fixes to support a wider set of RAML contracts |