Moritz Schepp

Thanks for your quick reply! I just had a look at parser.rb and options.rb. It seems that the parsing actually happens in the `Slop::Options` class. The parser does reset the...

You can also remove the validator for the taggable association: ```ruby # config/initializers/aato.rb chain = ActsAsTaggableOn::Tagging.send(:get_callbacks, :validate) callback = chain.find{|cb| cb.filter.attributes == [:taggable]} chain.delete(callback) ``` Works on rails 5.1 with...

Thanks a lot for taking the time to look into this. Unfortunately, using sqlite3 as you suggest, would require the sqlite gem to be installed as well as the system...

Ha, good point! I feel that "Use empty lines between method definitions and also to break up methods into logical paragraphs internally." (for the first example) leaves some room for...

Theoretically, we could allow ALL guests (because they are internally represented by a single user called `guest`) the same set of personal groups but I think this might be very...

So let's say we'd attach a personal group of entities to a browser session. In this case the group would be lost (or at least irretrievable) once the browser is...

I understand that you are surprised by this behavior, but I'm afraid, this is how the process was designed: Since relationships can have properties (and by now also datings), we...

Note: The example we saw here is that a result having the search term in `distinct_name` was expected to have a higher relevance than one with several matches in `related.*`.

not reproducible in v3.0.3, perhaps problem only occurs in v3.1?

Also not reproducible with code from v3.1 merged to v3.0. Moving to v4.1.0 for verification after v3.1 features are merged into v4.0.