-
Notifications
You must be signed in to change notification settings - Fork 600
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
[Navigation Material] Migrate or provide an M3 alternative #1480
Comments
is there any updates on this? |
What dependency are you waiting for? |
Any updates on this? |
Curious on the state of this, is there a roadmap anywhere? Linter is now complaining, only a warning, but would be nice to no longer depend on material2 for just this component.
|
With the release of Compose Material 1.7.0-alpha04, the Material team has added a new artifact: As such, we are closing all issues here on Accompanist and will be fully deprecating Accompanist Navigation Material in an upcoming release. This issue was not fixed as part of the migration, so if you're still interested in this, please file an issue and the Material team will take a look. Include the link here so that others can star it! |
I created a ticket on the issue tracker here. Please star it. |
We had a solution (integration of M3's Bottomsheet to Navigation Compose) for some time and I finally open-sourced it. Who knows for how long :) |
NavigationMaterial is using Material 2, we either need to migrate it or provide an alternative version that references m3
The text was updated successfully, but these errors were encountered: