3.x.x - add s.deprecated_in_favor_of to reduce confusion when v4 not installed
#1552
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
joshdholtz
changed the title
s.deprecated_in_favor_of to reduce confusion when v4 not installed
|
I think this will need a new release, right? |
|
@NachoSoto Yup yup, it will! 😊 |
codykerns
approved these changes
Apr 29, 2022
Merged
|
awesome 😎 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Motivation
This question comes up quite often on why
v4has was not installed when runningpod installorpod updateand its becausev4is associated with the pod nameRevenueCatand notPurchasesDescription
Sets
deprecatedanddeprecated_in_favor_ofin the v3Purchasespodspec that will output theRevenueCatin now favored