soft-deprecate old generated LocalizedStringResource extensions #87
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
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.
Closes #81
In #82, we've introduced the static
LocalizedStringResource.localizable(_:)method which allows you to useString.Localizablein order to create aLocalizedStringResourceinstance with the similar sugar thatLocalizedStringResource.String...andLocalizedStringResource.localizableprovided:It's not so obvious what the difference is with type inference, so to explain some more:
This means that it's no longer worth the effort to generate
LocalizedStringResource.Stringand as a result, we're going to remove it.Before doing that though, I am going to mark it as soft-deprecated. This means to add the deprecation annotation but without triggering a warning (by setting the version number to 100000).
This will go live with 0.4.0. Then, in 0.5.0, I'll make the deprecation produce a warning and in 1.0.0, i'll remove the legacy generated code entirely.