We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
From the README:
YupNopeBooleans = Virtus.model { |mod| mod.coerce = true mod.string.boolean_map = { 'yup' => true, 'nope' => false } }
I would get undefined method string for Virtus::Configuration...
But I managed to get it working by going deeper on the object.
mod.coercer.config.string.boolean_map = { 'yup' => true, 'nope' => false }
Is there a mistake in the readme or am I missing something?
The text was updated successfully, but these errors were encountered:
That's an error in the readme ;(
On Wed, Apr 2, 2014 at 9:21 PM, Luke Fender notifications@github.com wrote:
From the readme: YupNopeBooleans = Virtus.model { |mod| mod.coerce = true mod.string.boolean_map = { 'yup' => true, 'nope' => false } } I would get undefined method string for Virtus::Configuration... But I managed to get it working by going deeper on the object. mod.coercer.config.string.boolean_map = { 'yup' => true, 'nope' => false } Is this intentional? Reply to this email directly or view it on GitHub: #258
From the readme:
I would get undefined method string for Virtus::Configuration... But I managed to get it working by going deeper on the object.
Reply to this email directly or view it on GitHub: #258
Sorry, something went wrong.
#259
No branches or pull requests
From the README:
I would get undefined method string for Virtus::Configuration...
But I managed to get it working by going deeper on the object.
Is there a mistake in the readme or am I missing something?
The text was updated successfully, but these errors were encountered: