How does one disable the big red warning message?

[iambumblehead]

I've updated inferno and redux in an application using react-toastify. Because react-toastify uses 'legacy' lifecycle functions, inferno prints the following red message to the console,

Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.
      TransitionGroup contains the following legacy lifecycles:
      componentWillMount
componentWillReceiveProps
      The above lifecycles should be removed.

Is it safe to use inferno with react-toastify? If so, how should one disable the warning message?

[iambumblehead]

inferno team / @Havunen,

The response in this related ticket is detailed and may interest you fkhadra/react-toastify#323 (comment)

[Havunen]

We could add same __suppressDeprecationWarning that React uses. Its development warning anyway

[Havunen]

@iambumblehead
If you want to contribute the code change, the place where this change could be implemented is here:

inferno/packages/inferno/src/DOM/utils/componentutil.ts

Lines 7 to 30 in 21b11ee

	function warnAboutOldLifecycles(component) {
	const oldLifecycles: string[] = [];
	if (component.componentWillMount) {
	oldLifecycles.push('componentWillMount');
	}
	if (component.componentWillReceiveProps) {
	oldLifecycles.push('componentWillReceiveProps');
	}
	if (component.componentWillUpdate) {
	oldLifecycles.push('componentWillUpdate');
	}
	if (oldLifecycles.length > 0) {
	warning(`
	Warning: Unsafe legacy lifecycles will not be called for components using new component APIs.
	${getComponentName(component)} contains the following legacy lifecycles:
	${oldLifecycles.join('\n')}
	The above lifecycles should be removed.
	`);
	}
	}

Remember test cases :)

[alanlima]

Hey @Havunen / @iambumblehead,

If it is ok, I can submit a PR to close this issue.

I was playing around with inferno's source code and I managed to finish it.

@iambumblehead if you are already working on this issue, please ignore me ;). I just started because I would like to learn anyway and end up finishing it. 🙃

[iambumblehead]

@alanlima that is awesome! I have not worked on this issue and am looking forward to using your changes.

[alanlima]

Hi guys,

@Havunen I submitted the PR but there is a branch restriction (probably because I did PR from master branch).
I read the contribution guide and the PR should be done under dev branch, but there is any. Should I create it on my repository first?

[Havunen]

@alanlima

I removed the docs about dev branch. Dev branch no longer exists, it was just more maintenance for me.

[Havunen]

PR for this ticket has been merged. I will create new release.

[Havunen]

7.1.11 released