Steve Richert

Same issue here. Definitely not the expected behavior.

It looks like this may be my fault. The problem is that `ActiveRecord::Base.attribute_condition` only started accepting two arguments when it started supporting end-exclusive ranges, starting at ActiveRecord 2.3.1. I see...

Could be. I defer to Ben.

We're also pointing to master to work around an issue with version 1.0.1. Could we please release current master as v1.0.2? Thank you!

Restarting that particular job. Recently, the suite has been experiencing some intermittent failures and I haven't had the chance to get to the bottom of it yet. :cry: :panda_face:

I have a few suggestions and concerns. First, let's call the variable `FIGARO_PATH`. Next, I think this feature would be more useful if the user could specify _any_ path on...

@vfonic Figaro 2.0 (in development) adds a `figaro exec` command, which uses Ruby to load your Figaro configuration into `ENV` and then execute some other command of your choosing. I'm...

I'm also very open to the creation of a JS Figaro sidecar (by somebody else! 😜), although I might suggest avoiding replicating Figaro v1 at this point, in favor of...

**Update:** After mulling this over some more, I'm leaning toward a single YAML configuration file with the ability to key the file according to the application environment. To define the...

Are you using Spring? If so, restart Spring and let me know if that works.