Commits on Oct 13, 2017

1. Adds environment boolean checks …

   Amber currently ships with 3 different environments: development, test
   and production.
   
   As a developer I would like to sometimes run code conditionally
   depending on the environment that the application is.
   
   ```crystal
   if Amber.env.development?
     # ... code here ...
   end
   
   ```
   
   This PR addresses the issue by creating a Amber::Env module that
   contains 3 module methods:
   
   ```crystal
   Amber.env.development?
   Amber.env.test?
   Amber.env.production?
   Amber.env.integration?
   Amber.env.staging?
   Amber.env.sandbox?
   
   Amber.env.in? %w(development test)
   Amber.env.in? %i(development test)
   
   Amber.env.is? "test"
   Amber.env.is? :test
   ```
   
   With the changes in this PR a developer should be able to call the
   appropriate method to check for the desired environment.
   
   Adds Additional Module methods
   
   `in?` and `is?` methods to check for inclusion of the environments
   
   Uses rails style for Amber environment checks

   

   eliasjpr committed Oct 13, 2017
   Configuration menu

   • View commit details
   • Copy full SHA for 3058844
   • Browse repository at this point

   Copy the full SHA

   3058844 View commit details

   Browse the repository at this point in the history