-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
config(): Add safety falback for when running in production #11686
Merged
Merged
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
/** | ||
* External dependencies | ||
*/ | ||
import { expect } from 'chai'; | ||
|
||
/** | ||
* Internal dependencies | ||
*/ | ||
import config from '../'; | ||
|
||
const NODE_ENV = process.env.NODE_ENV; | ||
const fakeKey = 'where did all the errors go?'; | ||
|
||
describe( '#config', () => { | ||
afterEach( () => process.env.NODE_ENV = NODE_ENV ); | ||
|
||
it( `should throw an error when given key doesn't exist (NODE_ENV == development)`, () => { | ||
process.env.NODE_ENV = 'development'; | ||
|
||
expect( () => config( fakeKey ) ).to.throw( ReferenceError ); | ||
} ); | ||
|
||
it( `should not throw an error when given key doesn't exist (NODE_ENV != development)`, () => { | ||
const envs = [ | ||
'client', | ||
'desktop', | ||
'horizon', | ||
'production', | ||
'stage', | ||
'test', | ||
'wpcalypso', | ||
]; | ||
|
||
envs.forEach( env => { | ||
process.env.NODE_ENV = env; | ||
|
||
expect( process.env.NODE_ENV ).to.equal( env ); | ||
expect( () => config( fakeKey ) ).to.not.throw( Error ); | ||
} ); | ||
} ); | ||
} ); |
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wouldn't the above thrown error log to console? Or, if not, would it be enough to move
console.log
into theNODE_ENV
condition (since tests have their ownNODE_ENV
)?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
not sure what you mean @aduth - they both log to the console but logging to the console isn't the problem. the thrown error halts the execution of the current JavaScript thread and that causes the big problem because it kills code which does nothing more than import the broken modules
it's my belief right now that we want to make an annoying console message so that any of us can quickly identify the failures in production but we want to prevent those failures from cascading outward thus removing the error
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense 👍
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we add in some styling to differentiate our Calypso framework warnings from React errors? For example:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
in f987c75 I added some styling @gwwar - wha'd'ya think?