atelier_core 0.1.2

Rust native core model for the AWS Smithy IDL.
Documentation

Atelier: crate atelier_core

This crate provides a Rust native core model for the AWS Smithy Interface Definition Language.

crates.io docs.rs

This crate is the foundation for the Atelier set of crates, and provides the following components:

  1. The model structures themselves that represents a Smithy model This is the in-memory representation shared by all Atelier crates and tools.
  2. The model builder structures that allow for a fluent and easy construction of a core model.
  3. The prelude model containing the set of shapes defined in the Smithy specification.
  4. Traits for reading/writing models in different representations.
  5. Trait and simple implementation for a model registry.
  6. A common error module to be used by all Atelier crates.

Example

The following example demonstrates the builder interface to create a model for a simple service. The service, MessageOfTheDay has a single resource Message. The resource has an identifier for the date, but the read operation does not make the date member required and so will return the message for the current date.

use atelier_core::error::ErrorSource;
use atelier_core::model::builder::values::{ArrayBuilder, ObjectBuilder};
use atelier_core::model::builder::{
    Builder, ListBuilder, MemberBuilder, ModelBuilder, OperationBuilder, ResourceBuilder,
    ServiceBuilder, SimpleShapeBuilder, StructureBuilder, TraitBuilder,
};
use atelier_core::model::{Identifier, Model, ShapeID};

let model = ModelBuilder::new("example.motd")
    .shape(
        ServiceBuilder::new("MessageOfTheDay")
            .documentation("Provides a Message of the day.")
             .version("2020-06-21")
            .resource("Message")
            .into(),
    )
    .shape(
        ResourceBuilder::new("Message")
            .identifier("date", "Date")
            .read("GetMessage")
            .into(),
    )
    .shape(
        SimpleShapeBuilder::string("Date")
            .add_trait(TraitBuilder::pattern(r"^\d\d\d\d\-\d\d-\d\d$").into())
            .into(),
    )
    .shape(
        OperationBuilder::new("GetMessage")
            .readonly()
            .input("GetMessageInput")
            .output("GetMessageOutput")
            .error("BadDateValue")
            .into(),
    )
    .shape(
        StructureBuilder::new("GetMessageInput")
            .add_member(
                MemberBuilder::new("date")
                    .refers_to("Date")
                    .into(),
            )
            .into(),
    )
    .shape(
        StructureBuilder::new("GetMessageOutput")
            .add_member(MemberBuilder::string("message").required().into())
            .into(),
    )
    .shape(
        StructureBuilder::new("BadDateValue")
            .error(ErrorSource::Client)
            .add_member(MemberBuilder::string("errorMessage").required().into())
            .into(),
    )
    .into();

*/

Runnable Examples

Currently, there is simply one complete example, weather.rs in the examples directory. As usual this is executed via cargo in the following manner. It will print, using Debug, the weather example model from the Smithy quick start.

$ cargo run --example weather

Changes

Version 0.1.2

  • Updated the model and builder APIs to support JSON and Smithy readers:
    • added the HasMembers trait for a more un-typed API,
  • Finished the API documentation.

Version 0.1.1

  • Updated the model and builder APIs to be more consistent:
    • documented method patterns, and ensured they were applied,
    • moved from per-type build methods to use Into<T>,
  • Added the majority of API documentation.

Version 0.1.0

  • First release.
  • Initial types for manipulation of Smithy Models, not including selector expressions.
  • Initial builder types for fluent construction of models.
  • Able to construct the example weather service using the builder API.

TODO

  1. Complete the prelude model.
  2. Complete the selector expression types
  3. Complete the builder types
  4. Validation!
  5. Complete macro-ize APIs for less code
  6. More documentation
  7. More tests