Allows you to create a class that has multiple error surfaces registered but stays within the familiar territory of ActiveRecord::Validations.
| Project | DestinationErrors |
|---|---|
| gem name | destination_errors |
| license | MIT |
| expert support |  |
| download rank |  |
| version |  |
| dependencies |  |
| code quality |  |
| inline documenation |  |
| continuous integration |  |
| test coverage |  |
| homepage | on Github.com |
| documentation | on Rdoc.info |
| live chat |  |
| Spread |
🌏, 👼,  ,  , 🌹 |
Add this line to your application's Gemfile:
gem 'destination_errors'And then execute:
$ bundle
Or install it yourself as:
$ gem install destination_errors
Here is a contrived example.
You have three models, and a form that interacts with all of them:
class User
has_one :profile
has_one :account
end
class Profile
belongs_to :user
end
class Account
belongs_to :user
end
So you create an admin user form presenter class to handle everything, and you want it to be railsy.
class AdminUserFormPresenter
include DestinationErrors
attr_accessor :user, :profile, :account
has_error_surfaces [nil, :user, :profile, :account]
def initialize(*args)
@surface_errors_on = nil # nil means errors will be moved onto this instance.
end
end
For more example usage see the specs.
After checking out the repo, run bin/setup to install dependencies. Then, run bin/console for an interactive prompt that will allow you to experiment.
To install this gem onto your local machine, run bundle exec rake install.
To release a new version, update the version number in version.rb, and then run bundle exec rake release to create a git tag for the version, push git commits and tags, and push the .gem file to rubygems.org.
This library aims to adhere to Semantic Versioning 2.0.0. Violations of this scheme should be reported as bugs. Specifically, if a minor or patch version is released that breaks backward compatibility, a new version should be immediately released that restores compatibility. Breaking changes to the public API will only be introduced with new major versions.
As a result of this policy, you can (and should) specify a dependency on this gem using the Pessimistic Version Constraint with two digits of precision.
For example:
spec.add_dependency 'destination_errors', '~> 0.0'
- Fork it ( https://github.com/[my-github-username]/destination_errors/fork )
- Create your feature branch (
git checkout -b my-new-feature) - Commit your changes (
git commit -am 'Add some feature') - Push to the branch (
git push origin my-new-feature) - Make sure to add tests!
- Create a new Pull Request
See the Network View
