errors are not raised when update, update_columns, or destroy versions fail to create

[modosc]

paper_trail is inconsistent when Version records cannot be created. in some cases (create) an error is raised, in others (update, update_columns, and destroy) an error is logged but not raised. this can result in history silently being lost which is certainly unexpected behavior.

Currently when creating a new versioned record an error is raised if the Version cannot be created - this is because #save! is used:

paper_trail/lib/paper_trail/record_trail.rb

Line 62 in 47dbc22

version.save!

However, when updating, using update_columns, or destroying a versioned record no error is raised if the Version cannot be created:

paper_trail/lib/paper_trail/record_trail.rb

Line 111 in 47dbc22

if version.save

paper_trail/lib/paper_trail/record_trail.rb

Line 301 in 47dbc22

version = versions_assoc.create(data)

paper_trail/lib/paper_trail/record_trail.rb

Line 84 in 47dbc22

version = @record.class.paper_trail.version_class.create(data)

proposal

i think the behavior should be consistent - all failures should either raise errors or not. personally i don't see any advantage to not raising an error in these cases - it likely means that whodunnit isn't defined which i would expect to be an oversight rather than intentional. i realize this is not backwards compatible so i propose a two step process:

1. an opt-in configuration parameter is added to the current major version which causes update and destroy failures to raise an error.
2. in the next major version bump this becomes the default behavior.

does this seem reasonable? i'm happy to take this on asap.

[github-actions]

This issue has been automatically marked as stale due to inactivity.
The resources of our volunteers are limited.
Bug reports must provide a script that reproduces the bug, using our template. Feature suggestions must include a promise to build the feature yourself.
Thank you for all your contributions.

[modosc]

what do i have to do to get human eyes on this? this is a serious actual bug and i created a pr (complete with documentations and tests). is this project dead?