Daniel (dB.) Doubrovkine

icon indicating a website link https://code.dblock.org icon indicating an email [email protected]

icon company @opensearch-project icon location New York, NY icon location @opensearch-project, ex-@aws, former CTO @artsy @ArtsyOpenSource, @vestris, active maintainer of @ruby-grape, hashie, @slack-ruby, @playplayio and more.

Results 3350 comments of Daniel (dB.) Doubrovkine

NoMethodError: undefined method `where' for HistoryTracker:Class

It sounds like a separate (and real) problem @Ninigi.

NoMethodError: undefined method `where' for HistoryTracker:Class

I think you should and maybe try to write a spec for it? At the very least it's a bug, and your solution is a workaround, but we should actually...

NoMethodError: undefined method `where' for HistoryTracker:Class

What do we do with this issue here? Looks like `Mongoid.belongs_to_required_by_default` was required? Not sure I understand what's going on.

NoMethodError: undefined method `where' for HistoryTracker:Class

Okay, so I think what we need is either or both documentation that explains this in README and much better error messaging. Care to contribute @Ninigi?

A tracker on an embeds_many relation is being limited by the parent configuration

This exists for a reason I am sure, but will need a closer look. PR a fix with some specs and let's see what existing specs fail?

Adding Userstamp in mongoid 5

We still recommend the userstamp gem while it hasn't been supported since mongoid 4. Maybe someone cares to remove it from the documentation altogether or suggest an alternative?

Proposal: `history_tracks` method should be dynamically named

Makes total sense to me. I would preserve the ability to re-define the name for this in the declaration of course.

How can we track changes done with set method?

You can't today since it's one that doesn't invoke callbacks and is atomic.

Localized fields support

Rebase this and I can take a look

More maintainers for this repo

Thanks @mauriciozaffari for adding @Loschcode and @sveredyuk! Party on the code, make pull requests and ask for Rubygems access to make the next release, close this issue when one of...