README.markdown in roar-1.1.1 vs README.markdown in roar-1.2.0
- old
+ new
@@ -2,11 +2,11 @@
_Resource-Oriented Architectures in Ruby._
[](https://gitter.im/trailblazer/chat)
[](http://trailblazer.to/newsletter/)
-[](https://travis-ci.org/trailblazer/roar)
+[](https://github.com/trailblazer/roar/actions)
[](http://badge.fury.io/rb/roar)
## Table of Contents
* [Introduction](#introduction)
@@ -294,25 +294,25 @@
We're currently [working on](https://github.com/trailblazer/roar/issues/85) better strategies to easily implement `POST` and `PUT` semantics in your APIs without having to worry about the nitty-gritties.
## Coercion
-Roar provides coercion with the [virtus](https://github.com/solnic/virtus) gem.
+Roar provides coercion with the [dry-types](https://dry-rb.org/gems/dry-types/) gem.
```ruby
require 'roar/coercion'
require 'roar/json'
class SongRepresenter < Roar::Decorator
include Roar::JSON
include Roar::Coercion
property :title
- property :released_at, type: DateTime
+ property :released_at, type: Types::DateTime
end
```
-The `:type` option allows to set a virtus-compatible type.
+The `:type` option allows to set a dry-types-compatible type.
```ruby
song = Song.new
SongRepresenter.new(song).from_json('{"released_at":"1981/03/31"}')