Implement Typed Documents and TypeRegistry

[jterapin]

Description: Implementation for Typed Documents and TypeRegistry. Currently only supports JSON documents.

Customer Experience

Customer can instantiate a Document by using standard Ruby objects as its foundation:

string_doc = Smithy::Schema::Document.new('Hello World!')
string_doc.data
=> "Hello World!"

map_doc = Smithy::Schema::Document.new({ :name => 'Hamburger' })
map_doc.data
=> { "name" => "Hamburger" }

Customers can instantiate a Document with a runtime shape and its schema:

# given the following runtime shape:
typed_bird = BirdService::Types::Bird.new(name: 'Pidgey')
=> #<struct BirdService::Types::Bird name="Pidgey">

# provide runtime shape and its schema
bird_doc = Document.new(typed_bird, BirdService::Schema::Bird).data
=> { "name" => "Pidegey" }

When a runtime shape is used to create a Document, we capture the absolute shape id from its schema.

bird_doc.discriminator
=> "example.com#Bird"

Customers can reconstruct the runtime shape of a document by using as_typed method with a shape schema:

bird_doc.as_typed(BirdService::Schema::Bird)
=> #<struct BirdService::Types::Bird name="Pidgey">

Customers can use the TypeRegistry to find schema based on shape id:

BirdService::Schema::TypeRegistry.schema_by_id('somebird')
=> #<BirdService::Schema::Bird>

Remaining ToDos

• Add RBS support for public interfaces ONLY
• Add more Documentation (maybe)

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[jterapin]

I could add more details (e.g. code examples) but I might punt that to the Smithy-Ruby Wiki instead.

[mullermp]

I think in-code examples/documentation are preferred but it doesn't have to be done this moment.

[alextwoods]

Yea - I'd agree examples and more detail would be better as in code documentation.

[jterapin]

I will add them now - since information is very fresh in my head.