Skip to content

Reverted materialVersion back to 1.2.1#14431

Merged
khaykov merged 1 commit intodevelopfrom
issue/revert-material-lib-upgrade
Apr 9, 2021
Merged

Reverted materialVersion back to 1.2.1#14431
khaykov merged 1 commit intodevelopfrom
issue/revert-material-lib-upgrade

Conversation

@khaykov
Copy link
Copy Markdown
Contributor

@khaykov khaykov commented Apr 8, 2021

While working in TimeZone selector we bumped material library version from 1.2.1 to 1.3.0, and looks like this might have caused some issues (potentially related to new version of ConstraintLayout that 1.3.0 is using).

I only spotted the issue in reader, but it might appear somewhere else, so until we have more info on how to migrate to 1.3.0 I feel it's better to revert to 1.2.1

To test:

  • Open Reader.
  • Confirm that posts cards without Feature Images looks ok.

Post Cards should look like this:
Image from Gyazo

And not like this:
Image from Gyazo

PR submission checklist:

  • I have completed the Regression Notes.
  • I have considered adding accessibility improvements for my changes.
  • I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

@peril-wordpress-mobile
Copy link
Copy Markdown

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

@peril-wordpress-mobile
Copy link
Copy Markdown

You can test the changes on this Pull Request by downloading the APK here.

@ParaskP7 ParaskP7 self-assigned this Apr 9, 2021
@ParaskP7 ParaskP7 self-requested a review April 9, 2021 08:02
Copy link
Copy Markdown
Contributor

@ParaskP7 ParaskP7 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👋 @khaykov !

I have reviewed and tested this PR as per the instructions, everything works as expected, good fix! 🌟

While working in TimeZone selector we bumped material library version from 1.2.1 to 1.3.0.

Was bumping the material library a requirement for this work or was that an extra nice-to-have improvement? I am asking that because if that was a requirement I am not sure if I should be looking at a specific screen/feature to verify correctness with this revert. I did check the commit (2b085a6) that pumped the material library to 1.3.0, but I am still not 100% sure. Also, I am not sure whether bumping the core ktx is somehow related to that.

PS: Let me know your thoughts on the above. In the meanwhile, I will not merge this PR just yet.

@khaykov
Copy link
Copy Markdown
Contributor Author

khaykov commented Apr 9, 2021

Hey @ParaskP7 ! Thank you for the review! Regarding your question, it was nice to have improvement (We confirmed that there is no adverse effect on the original feature). I checked the change-log for material library, and it looked pretty innocent, so we went ahead with it.

@ParaskP7
Copy link
Copy Markdown
Contributor

ParaskP7 commented Apr 9, 2021

👋 @khaykov !

Perfect, I was thinking that, but played it safe and asked! 😅 Feel free to merge it with develop 🟢 light from my side.

@khaykov khaykov merged commit 921f3b4 into develop Apr 9, 2021
@khaykov khaykov deleted the issue/revert-material-lib-upgrade branch April 9, 2021 16:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants