Adrien S

I will. Just need some time to fix the specs and have CI run on github actions

In the meantime this works : ``` gem "premailer-rails", github: "Intrepidd/premailer-rails", branch: "support-propshaft" ```

Here y'all go ! ```ruby gem "premailer-rails-revived", "~> 1.12", require: "premailer/rails" ```

À priori c'est faisable facilement avec le devise paranoid mode : https://github.com/heartcombo/devise/wiki/How-To:-Using-paranoid-mode,-avoid-user-enumeration-on-registerable Ca dépend à quel point on a customizé tout ca. Je veux bien m'en charger.

Hey @FabioNascimento indeed it's an interesting use case. Having the exceptions in a config var like @jarthod suggested would work but I'm afraid it's limited as people will most likely...

Yup whenever I got a chance

Any idea on the naming ? `return_to_exclusive_working_time` & `return_to_inclusive_working_time` ? I'll keep `return_to_working_time` unchanged for now and just add a deprecation warning so we can remove it altogether in a...

Why not but in this case we must bump the major version number as this is a breaking change On Sat, 26 Dec 2015 at 10:45, Adrien Jarthon [email protected] wrote:...

Hi ! Thanks ! Several things : - You don't seem to need rspec-api-matchers anymore - It needs a spec testing behavior, that failed before, for example, set an unsorted...

It's more of a regression test. Your current test asserts the config is sorted, but does not ensure that everything still works. If later the code is changed and someone...