Conversation
This file contains hidden or 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
1 participant
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.
Description
Fix lifecycle rule rendering when one S3 rule contains both current-version and non-current-version actions. The UI now projects every lifecycle action and renders each version/duration pair in desktop tables and mobile cards, instead of pairing the non-current label with
Expiration.Days.Type of Change
Testing
Passed locally:
Related Issues
Closes #8036
Screenshots
The screenshots use the issue's two-rule payload (30/40 days and 10/20 days) and show the expected post-fix desktop and mobile layouts.
Additional Notes
The original S3 rule remains the deletion unit; the projected action list is display-only, so hidden lifecycle fields are not lost when a rule is deleted.