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

Should use Compose BOM instead of reference to specific compose version #186

Closed
1 of 2 tasks
carstenhag opened this issue Oct 29, 2023 · 1 comment · Fixed by #205
Closed
1 of 2 tasks

Should use Compose BOM instead of reference to specific compose version #186

carstenhag opened this issue Oct 29, 2023 · 1 comment · Fixed by #205
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@carstenhag
Copy link

carstenhag commented Oct 29, 2023

⚠️ Is your feature request related to a problem? Please describe

Nowdays it's recommended to use compose BOM versioning instead of hard references to using a specific version for all compose libraries. See https://developer.android.com/jetpack/compose/bom

💡 Describe the solution you'd like

A solution with version catalogs is explained at https://developer.android.com/jetpack/compose/bom#does_the_bom_work_with_version_catalogs. At work I am not using version catalogs yet so I can't get it working with a <2min PR 😢

🤚 Do you want to develop this feature yourself?

  • Yes
  • No (Note: At least not right now)
@cortinico
Copy link
Owner

This is a great point. I'm up for receiving a PR which introduces the compose BOM from you or anyone else who wants to do it 👍

@cortinico cortinico added help wanted Extra attention is needed good first issue Good for newcomers labels Oct 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants