[Merged by Bors] - Try to deprecate LSR field typo #2504
Closed
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
Found old TODO for a typo fix on next minor version bump Basically this is redoing infinyon#1298
|
bors r+ |
bors bot
pushed a commit
that referenced
this pull request
Jul 26, 2022
This is a PR that we need before fully changing from LSR to LRS #2392 Without actually renaming the field but adding support in advance to using both `lrs` and `lsr` in the deserialization of the status
|
Build failed: |
|
bors retry |
bors bot
pushed a commit
that referenced
this pull request
Jul 26, 2022
This is a PR that we need before fully changing from LSR to LRS #2392 Without actually renaming the field but adding support in advance to using both `lrs` and `lsr` in the deserialization of the status
|
Pull request successfully merged into master. Build succeeded: |
bors
bot
changed the title
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.
This is a PR that we need before fully changing from LSR to LRS #2392
Without actually renaming the field but adding support in advance to using both
lrsandlsrin the deserialization of the status