add accessor and regenerate tests

[phoet]

#14

@vfonic i think that this approach is the more rubyesque way to solve this issue. you would need to handle errors and maybe even have your own error-class to show improved error-messages or validation hints.

[vfonic]

This pretty-much works. The difference is that, in order to see the detailed explanation of the error (problems), you'll have to catch the error and then do error.problems. Otherwise, in the terminal console, you'll only see Validation Error with no explanation.

So I'm not sure if adding the full error immediately is better.

[vfonic]

If this line doesn't raise, this (and preview test) will pass, without actually testing anything.

[vfonic]

This is strange. We also have this test when testing our after_destroy callback: https://github.com/vfonic/webflow_sync/blob/master/spec/jobs/webflow_sync/destroy_item_job_spec.rb#L38

[vfonic]

Here's how rails does it:

[1] pry(main)> doc = Document.new;
[2] pry(main)> doc.save!
ActiveRecord::RecordInvalid: Validation failed: Entity must exist, Municipality must exist, File url can't be blank, Title can't be blank, Type is not included in the list
from /Users/viktor/.rvm/gems/ruby-2.6.6/gems/activerecord-6.0.3.4/lib/active_record/validations.rb:80:in `raise_validation_error'

It returns all of the validation errors joined together in a single string:
https://github.com/rails/rails/blob/main/activerecord/lib/active_record/validations.rb#L22

[vfonic]

Thank you, @phoet! 🚀