Print deprecation message only on usage of the returned .js() and .css() value #57
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.
From V3 to V4 we deprecated the return value from the
.js()
and.css()
methods. In V5 we will remove that these return a value.Due to this an deprecation message was added but the deprecation message is printed when these methods are used. Calling these methods to set a value will trigger the deprecation message which are not quite what we want.
This little hack makes it so that the deprecation message is printed only when one try to use the returned value from these methods.
This will not trigger a deprecation message:
This will trigger a deprecation message: