Tom Lord
Tom Lord
I think a better solution would be to add a post-install message, explaining what had just happened. For example, a warning about which version of bundle you installed would be...
Rails 5 has built-in support for UUID primary keys, so ideally you should migrate away from this gem...
Slightly simpler version (using ActiveSupport, so this is basically rails-only): ``` def valid_email_address(address) mail_address = Mail::Address.new(address) mail_address.local.present? && mail_address.domain.present? rescue Mail::Field::FieldError false end ```
> Standard devise setup, standard devise_invitable setup. Using included views and no controller overrides. If this is the case, it sounds like a major issue. I don't have the time...
I don't see why that should be the responsibility of this gem.
This doesn't work on firefox. Here's a minimal fix: ``` if (error.message === 'Failed to fetch' || error.message === 'NetworkError when attempting to fetch resource.') { adBlocked = true; }...
What's the full error trace? Only showing the top line of the error with no context makes this difficult to understand.
I like the idea, but I suppose this problem should be solved be a separate gem - what do you think? For example, we could have `RegexpNegator.new(regex) #=> negated_regex` Or...
...But what does a negated `/hello/` actually look like? Without using irregular aspects of regex (i.e. look-arounds), that is. I suspect this may closely relate to [this problem](https://github.com/tom-lord/regexp-examples/issues/22) I encountered...