Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resolve UsingMaterialAndMaterial3Libraries errors #21065

Closed
14 tasks
nbradbury opened this issue Jul 22, 2024 · 1 comment · Fixed by #21583
Closed
14 tasks

Resolve UsingMaterialAndMaterial3Libraries errors #21065

nbradbury opened this issue Jul 22, 2024 · 1 comment · Fixed by #21583

Comments

@nbradbury
Copy link
Contributor

nbradbury commented Jul 22, 2024

We have a lot of screens that use a mix of Material and Material3 components, resulting in UsingMaterialAndMaterial3Libraries lint errors (which used to be warnings). Tackling these all at once would be a large task, but we can at least tackle them individually over time.

For now we're adding this to lint.xml to pass lint checks, but this is a short-term solution:

<issue id="UsingMaterialAndMaterial3Libraries" severity="warning" />

This is a short list of screens and components we should migrate to Material 3. There are many more of them, but this is a start.

  • BaseState.kt
  • BlazeCampaignsCard.kt
  • BlazeOverlayFragment.kt
  • BlazePromoteWebViewFragment.kt
  • BlazeStatusLabel.kt
  • BloganuaryNudgeCard.kt
  • BloganuaryNudgeLearnMoreOverlay.kt
  • BloggingPromptsListItem.kt
  • BloggingPromptsListScreen.kt
  • ButtonsColumn.kt
  • CampaignDetailFragment.kt
  • CampaignListRow.kt
  • CampaignListingFragment.kt
  • CloseAccountButton.kt
@dangermattic
Copy link
Collaborator

dangermattic commented Jul 22, 2024

Thanks for reporting! 👍

@nbradbury nbradbury changed the title Resolve UsingMaterialAndMaterial3Libraries erros Resolve UsingMaterialAndMaterial3Libraries errors Jul 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants