verifying existence bugsnag in service file - issue #42 #48
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change verifies if there’s an option for bugsnag in `config/services.php` file. if so, it gets `$config` from there. Therefore, it’s possible to retrieve API key from that file versus creating a new `bugsnag.php` file
|
Thanks for fixing this @ehkasper! This looks great. I'm going to go ahead and merge this in. |
jessicard
added a commit
that referenced
this pull request
Apr 27, 2015
verifying existence bugsnag in service file - issue #42
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change verifies if there’s an option for bugsnag in
config/services.phpfile. if so, it gets$configfrom there.Therefore, it’s possible to retrieve API key from that file versus
creating a new
bugsnag.phpfile.This closes #42