Comments (2)
I was wondering about something like:
on_create :increment, if: ->(student) { student.subscribed? && student.confirmed? }
on_delete :decrement, if: ->(student) { student.subscribed? && student.confirmed? }
on_update :increment, if: ->(student) { student.has_changed? :subscribed_at, from: nil, to: Counter::Any }
on_update :increment, if: ->(student) { student.has_changed? :confirmed, from: false, to: true }
on_update :decrement, if: ->(student) { student.has_changed? :subscribed_at, from: Counter::Any, to: nil }
on_update :increment, if: ->(student) { student.has_changed? :confirmed, from: true, to: false }
i.e., be explicit about increment/decrement so we don't need to return numbers, and allow multiple checks for update.
from counter.
???
increment_on_create_if ->(student) { student.subscribed? && student.confirmed? }
decrement_on_delete_if, ->(student) { student.subscribed? && student.confirmed? }
increment_on_update_if ->(student) { student.has_changed? :subscribed_at, from: nil, to: Counter::Any }
increment_on_update_if ->(student) { student.has_changed? :confirmed, from: false, to: true }
decrement_on_update_if: ->(student) { student.has_changed? :subscribed_at, from: Counter::Any, to: nil }
decrement_on_update_if ->(student) { student.has_changed? :confirmed, from: true, to: false }
or maybe
on :create do
increment_if ->(student) { student.subscribed? && student.confirmed? }
end
on :delete do
decrement_if ->(student) { student.subscribed? && student.confirmed? }
end
on :update do
increment_if ->(student) { student.has_changed? :subscribed_at, from: nil, to: Counter::Any }
increment_if ->(student) { student.has_changed? :confirmed, from: false, to: true }
decrement_if ->(student) { student.has_changed? :subscribed_at, from: Counter::Any, to: nil }
decrement_if ->(student) { student.has_changed? :confirmed, from: true, to: false }
end
from counter.
Related Issues (13)
- Naming things
- `keep_count_of`⁉️
- Can you directly use `Counter::Value` or must you subclass?
- Support on change events for counters
- Use the definition class name as the name of the counter (Counter::Value#name)
- Rename the repo and move to Counterwise namespace
- Rethink the singleton approach?
- Lazy loading in dev breaks things
- Add `join_counter_data` to support filtering on the counter data
- Support historical data points or data ranges
- Support global counters that count all instances of a model e.g. Student.count
- How best to support different underlying value storage models?
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 counter.