Conversation
|
Hi @anicholson, I quickly investigated the reasons for the errors you reported, and I think I'll have to make small adjustments to ensure support not only the Virtus in its latest version, but also to other changes in other GEMS and also in Ruby itself. As you can see, I did not mention inside Gemspec the version of Virtus that I intend to use, so if you are having trouble using the json-schematized, you can set the version of Virtus that works for you. Example: # Gemfile
gem 'json-schematized'
gem 'virtus', '~>0.5.0'I'll be working to ensure support for the latest version of Virtus. Thanks. |
|
Thanks Marcelo :) It's a very cool Gem :) — On Thu, Nov 28, 2013 at 9:19 PM, Marcelo Manzan notifications@github.com
|
|
Hi @anicholson, This repo is deprecated and I fixed this problem through pull-request #4, and now my fork is the official repo of this GEM. Please try to use the last version of the json-schematized gem to check if the last Virtus version finely works for you too. Regards. |
This is a fix for Issue #2 : the API for Virtus has changed from 0.5.x to 1.x.
I'm not sure exactly what's changed, or what's needed to make this work with the newer version of Virtus,
but this at least gets things working again from clean installs :)