Deprecating behaviours about lifecycle HOT 7 CLOSED

I think details has this covered.

from lifecycle.

The warning message will either refer to a function or to an argument so I don't think details is sufficient here. We don't want to mislead the user into thinking a whole function is deprecated.

I was thinking we need something like 0 suffixed variants which take a raw message instead of a spec.

from lifecycle.

Do you have a specific case where we've deprecated something that isn't a function or argument?

from lifecycle.

I don't remember exactly, I think it was some kind of global or contextual state. Deprecating a global option (or one its values) would be an example.

from lifecycle.

FYI, just found this closed issue while searching how to deprecate a global option. 👀

from lifecycle.

This is now discussed in #120.

from lifecycle.

Thank you @lionel- !

from lifecycle.