Steve Richert

Would you be willing to contribute a failing test?

There's already [a test](https://github.com/laserlemon/figaro/blob/7d950c1c100f93142373ed9a1ef00868fa9d30a5/spec/rails_spec.rb#L40-L48) that asserts that `ENV` is set immediately after the Rails application is defined, exactly as is described in the initial code example. This test is run...

It would be a start. The test suite actually generates a brand new Rails 4.2 app and then modifies it in different ways to test its behavior, so it'd still...

Okay, thanks. I just did a little digging and here's what I came up with… My test works because this is the code I test to ensure configuration is available...

Issue submitted. :point_up:

:+1:

As of today, we should hardcore the path because that's exactly where Figaro will look for it. Thank you for checking on this!

Are the values in your `application.yml` set as integers or as strings?

@joallard It's always helpful if you can give me some code to work with: a failing test and/or a proposed solution.

While I agree that the `heroku:set` command should convert to strings (with warnings) as Figaro does elsewhere, `application.yml` values should also be set to strings. I now have a failing...