You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, I wanted to share a few ideas and learn how receptive the maintainers would be to them.
The ohm-contrib repo is very dormant, albeit mostly stable. I think it would be smart to move Ohm::Timestamps, Ohm::DataTypes and Ohm::Callbacks move to core (as plugins). Not a lot of code, and I think widely useful functionality.
I'd like to be able to use sorted indices that support chained queries in Ohm. I think ranged queries (eg. for timestamp comparisons) are core functionality, and Redis obviously has built in support for this kind of data type. ohm-sorted is nice syntactically, but chaining fails in Stal.
Just an opinion, but I think #attributes should include model :id. Semantically, I think it's accurate to call the primary key an attribute of the model.
All IMHO obviously. Thanks you as always for the software and the time.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello, I wanted to share a few ideas and learn how receptive the maintainers would be to them.
Ohm::Timestamps,Ohm::DataTypesandOhm::Callbacksmove to core (as plugins). Not a lot of code, and I think widely useful functionality.#attributesshould include model:id. Semantically, I think it's accurate to call the primary key an attribute of the model.All IMHO obviously. Thanks you as always for the software and the time.
Beta Was this translation helpful? Give feedback.
All reactions