{"issue":{"state":"open","pull_request":{"diff_url":null,"html_url":null,"patch_url":null},"milestone":null,"user":{"avatar_url":"https://secure.gravatar.com/avatar/49a9f6ddba9fda187ba12f15731da4b5?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"49a9f6ddba9fda187ba12f15731da4b5","url":"https://api.github.com/users/akhawaja","login":"akhawaja","id":1026071},"assignee":null,"updated_at":"2011-11-15T07:27:40Z","labels":[],"closed_at":null,"comments":6,"url":"https://api.github.com/repos/laravel/laravel/issues/152","body":"This pertains to Laravel 2.0.\r\n\r\nIdeally, aliases should be removed from the config/application.php file.  When you update Laravel, the only folder that should be updated is the \"laravel\" folder.  The application folder should only contain user generated code.  By consistently updating the config/application.php file, it makes it challenging to just replace the \"laravel\" folder.","html_url":"https://github.com/laravel/laravel/issues/152","title":"[Request] Remove aliases from config/application.php","number":152,"id":2218265,"created_at":"2011-11-12T19:02:28Z"},"action":"created","comment":{"user":{"avatar_url":"https://secure.gravatar.com/avatar/fd3e5171cbc1f277daacacef4967bceb?d=https://a248.e.akamai.net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-140.png","gravatar_id":"fd3e5171cbc1f277daacacef4967bceb","url":"https://api.github.com/users/sparksp","login":"sparksp","id":243893},"updated_at":"2011-11-15T07:27:40Z","url":"https://api.github.com/repos/laravel/laravel/issues/comments/2741809","body":"Yes, perhaps this is the best way.  It is quite easy in Laravel to accomplish this.  I guess Taylor is still deciding how much config stuff to put in application/ and how much to put in to laravel/ - each config file that goes into laravel/ is another file that will get loaded with most requests.","id":2741809,"created_at":"2011-11-15T07:27:40Z"}}