Skip to content
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

Change warning text: 'a uncontrolled' --> 'an uncontrolled' #6591

Closed
wants to merge 1 commit into from

Conversation

bportnoy
Copy link

Changes new React 15 warning regarding controlled component status switching to properly use "an" rather than "a" before "uncontrolled," which begins with a vowel sound.

@@ -7966,7 +7966,7 @@ var ReactDOMInput = {
var owner = inst._currentElement._owner;

if ((initialValue || !inst._wrapperState.controlled) && controlled && !didWarnUncontrolledToControlled) {
"development" !== 'production' ? warning(false, '%s is changing a uncontrolled input of type %s to be controlled. ' + 'Input elements should not switch from uncontrolled to controlled (or vice versa). ' + 'Decide between using a controlled or uncontrolled input ' + 'element for the lifetime of the component. More info: https://fb.me/react-controlled-components', owner && owner.getName() || 'A component', props.type) : void 0;
"development" !== 'production' ? warning(false, '%s is changing an uncontrolled input of type %s to be controlled. ' + 'Input elements should not switch from uncontrolled to controlled (or vice versa). ' + 'Decide between using a controlled or uncontrolled input ' + 'element for the lifetime of the component. More info: https://fb.me/react-controlled-components', owner && owner.getName() || 'A component', props.type) : void 0;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file is auto-generated and does not need to be modified.

@jimfb
Copy link
Contributor

jimfb commented Apr 28, 2016

@bportnoy Can you update this PR to not update the auto-generated files. Other than that, I think this is ready-to-go.

@jimfb
Copy link
Contributor

jimfb commented May 2, 2016

superceded by #6657

@jimfb jimfb closed this May 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants