react

mirror of https://github.com/zebrajr/react.git synced 2025-12-07 00:20:28 +01:00

History

Sunil Pai d9b4c55d53 unify deprecated/unsafe lifecycle warnings, pass tests (#16103 ) - redoes #15431 from scratch, taking on the feedback there - unifies the messaging between "deprecated" and UNSAFE_ lifecycle messages. It reorganizes ReactStrictModeWarnings.js to capture and flush all the lifecycle warnings in one procedure each. - matches the warning from ReactPartialRenderer to match the above change - passes all the tests - this also turns on `warnAboutDeprecatedLifecycles` for the test renderer. I think we missed doing so it previously. In a future PR, I'll remove the feature flag altogether. - this DOES NOT do the same treatment for context warnings, I'll do that in another PR too	2019-07-15 20:56:44 +01:00
..
print-warnings.js	unify deprecated/unsafe lifecycle warnings, pass tests (#16103 )	2019-07-15 20:56:44 +01:00
README.md	Fix the print warnings script (#9344 )	2017-04-05 18:54:48 +01:00

unify deprecated/unsafe lifecycle warnings, pass tests (#16103 )

- redoes #15431 from scratch, taking on the feedback there
- unifies the messaging between "deprecated" and UNSAFE_ lifecycle messages. It reorganizes ReactStrictModeWarnings.js to capture and flush all the lifecycle warnings in one procedure each.
- matches the warning from ReactPartialRenderer to match the above change
- passes all the tests
- this also turns on `warnAboutDeprecatedLifecycles` for the test renderer. I think we missed doing so it previously. In a future PR, I'll remove the feature flag altogether.
- this DOES NOT do the same treatment for context warnings, I'll do that in another PR too

2019-07-15 20:56:44 +01:00

print-warnings.js

unify deprecated/unsafe lifecycle warnings, pass tests (#16103 )

2019-07-15 20:56:44 +01:00

README.md

Fix the print warnings script (#9344 )

2017-04-05 18:54:48 +01:00

README.md

We use this script to extract all messages from warning() calls. They don't get substituted with anything in the source or the build. We only do this so we can have a copy of these messages in our internal repository and can spot accidental changes to them.