Comments (1)
We are running into a similar situation where we have a weird setup with a shared module that defines logic between two ActiveRecord classes that write to the same database table and are treated as the same entity.
We want to be able to track the history as a single entity, doesn't matter which of the two classes triggered the change. This looks like:
class Shared
extend ActiveSupport::Concern
included do
self.table_name "shared_model"
has_paper_trail(
meta: {
item_type: "SharedModel"
}
)
end
end
class Foo
include Shared
end
class Bar
include Shared
end
After the upgrade to PaperTrail 14 this is now also throwing an error. And if we would remove the item_type
setting it would result in the versions table having entries for Foo
and Bar
instead of SharedModel
.
If possible we would also like to have an option to configure this somewhere.
from paper_trail.
Related Issues (20)
- Change the Versions table name HOT 4
- Support Rails 7.1 HOT 5
- Drop RequestStore in favor of ActiveSupport::CurrentAttributes HOT 6
- errors are not raised when update, update_columns, or destroy versions fail to create HOT 2
- Install migrations --with-changes use text column but PaperTrail errors with expecting JSON or JSONB HOT 1
- `versions` association adding an additional and invalid ORDER BY statement HOT 3
- Only track changes for updates; still track creation and destruction events HOT 3
- Incompatible with ActiveRecord 7's composite primary keys HOT 4
- Ignore certain columns by default HOT 2
- yaml_column_permitted_classes warning never actually gets output HOT 2
- `PaperTrail::Version.where_object` cannot not find serialized values in YAML object HOT 1
- Date/DateTime leads to empty changeset HOT 4
- Ability to conditionally set metadata on a version record depending on the event (create, update, etc) HOT 1
- `versions` raises error whenever `PaperTrail::Version` is a parent to an abstract superclass HOT 1
- Empty "update" versions when using active storage HOT 3
- errors are not raised when update, update_columns, or destroy versions fail to create
- reify tries to set the value for a read_only attribute HOT 1
- Tests fail on master - rspec ./spec/paper_trail/request_spec.rb:120 HOT 4
- Calling has_paper_trail on STI models causes 2 inserts to versions HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from paper_trail.