compose-destinations

Annotation processing library for type-safe Jetpack Compose navigation with no boilerplate.

APACHE-2.0 License

Stars
3.1K

Bot releases are hidden (Show)

compose-destinations - 2.1.0-alpha02

Published by raamcosta 8 months ago

What changed from alpha01

  • DestinationStyle.Animated now has getters for lambdas rather than functions. This allows users to keep some of them as null so that it is more 1 to 1 to the official navigation library.
  • Removed dependency from accompanist! 🙌 Bottom sheets are not provided by the new alpha material navigation artifact!
  • Added new sizeTransform to DestinationStyle.Animated

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/2.1.0-alpha01...2.1.0-alpha02

compose-destinations - 2.0.0-alpha02

Published by raamcosta 8 months ago

What changed from alpha01

  • DestinationStyle.Animated now has getters for lambdas rather than functions. This allows users to keep some of them as null so that it is more 1 to 1 to the official navigation library.

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/2.0.0-alpha01...2.0.0-alpha02

compose-destinations - 2.1.0-alpha01

Published by raamcosta 8 months ago

First v2 alpha release 🙌 (compose 1.7 - alpha dependencies)

This release brings a bunch of improvements both in ergonomics of using the library, features, fixes, better documentation about nav graphs, and more!

I'm still working on the actual documentation for v2 specific changes and features, but for now, I would reallly appreciate it if you could try it, and let me know how it goes.
There are some breaking changes, I did want to take advantage of a major release to improve things I was avoiding until now, so you need to go through this steps here (some are conditional). Please do let me know if you find something in migrating which is not documented there, or is not clear enough.

https://composedestinations.rafaelcosta.xyz/migrating-to-v2

Thank you so much for sticking with Compose Destinations, I assure you these changes are worth it already and they also help me evolve the library even more in the future! 🙇

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.11.1-alpha...2.1.0-alpha01

compose-destinations - 2.0.0-alpha01

Published by raamcosta 8 months ago

First v2 alpha release 🙌 (compose 1.6)

This release brings a bunch of improvements both in ergonomics of using the library, features, fixes, better documentation about nav graphs, and more!

I'm still working on the actual documentation for v2 specific changes and features, but for now, I would reallly appreciate it if you could try it, and let me know how it goes.
There are some breaking changes, I did want to take advantage of a major release to improve things I was avoiding until now, so you need to go through this steps here (some are conditional). Please do let me know if you find something in migrating which is not documented there, or is not clear enough.

https://composedestinations.rafaelcosta.xyz/migrating-to-v2

Thank you so much for sticking with Compose Destinations, I assure you these changes are worth it already and they also help me evolve the library even more in the future! 🙇

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.10.2...2.0.0-alpha01

compose-destinations - 1.11.1-alpha

Published by raamcosta 8 months ago

compose-destinations - 1.10.2

Published by raamcosta 8 months ago

compose-destinations - 1.11.0-alpha

Published by raamcosta 8 months ago

What changed

  • Updated dependencies to 1.7 alpha on navigation and compose ui

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.10.1...1.11.0-alpha

compose-destinations - 1.10.1

Published by raamcosta 8 months ago

** What changed

  • Updated dependencies to latest 1.6 compose stable

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.10.0...1.10.1

compose-destinations - 1.10.0

Published by raamcosta 9 months ago

Changes

  • Update to Compose 1.6
  • Fixed an issue with having line comments after nav arguments with certain default values

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.63...1.10.0

compose-destinations - 1.9.63

Published by raamcosta 9 months ago

Changes

  • Fixed an issue with having line comments after nav arguments with certain default values

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.62...1.9.63

compose-destinations - 1.9.62

Published by raamcosta 9 months ago

Changes

  • Another fix related to default value parsing

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.61...1.9.62

compose-destinations - 1.9.61

Published by raamcosta 9 months ago

Changes

  • Fixed regression caused by 1.9.60 changes

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.60...1.9.61

compose-destinations - 1.9.60

Published by raamcosta 9 months ago

compose-destinations - 1.9.59

Published by raamcosta 9 months ago

compose-destinations - 1.9.58

Published by raamcosta 9 months ago

Changes

  • Fixed #524
  • Fixed an issue where ResultRecipients were not considering the correct Destination as sender when validating types, in some specific scenarios

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.57...1.9.58

compose-destinations - 1.9.57

Published by raamcosta 10 months ago

What changed

  • Fixes #541
  • We now allow a parameter on the annotated Composable of the same type of the navArgsDelegate even if (and this is the new bit) that type is also a navigation argument type.
    So, this:
@Serializable
data class SomeSerializable(...)

@Destination(
    navArgsDelegate = SomeSerializable:class
)
@Composable
fun SomeScreen(
    navArgs: SomeSerializable
)

Will now work, and navArgs parameter will be provided by the library.
Before, since navArgs is Serializable, Compose Destinations would treat it as a new nav argument, but since you were specifying a delegate to define the nav args, it didn't allow you to do that.

NOTE that the navArgsDelegate class doesn't need to be Serializable itself, each field will corresponde to one nav argument, so only the fields need to be considered a nav argument type. (list is on https://composedestinations.rafaelcosta.xyz/destination-arguments/navigation-arguments#basics).

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.56...1.9.57

compose-destinations - 1.9.56

Published by raamcosta 10 months ago

What's Changed

New Contributors

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.55...1.9.56

compose-destinations - 1.9.55

Published by raamcosta 11 months ago

Versions update:

  • Compose navigation to 2.7.5
compose-destinations - 1.9.54

Published by raamcosta about 1 year ago

compose-destinations - 1.9.53

Published by raamcosta about 1 year ago

Versions update

  • Compose 1.5.1
  • Kotlin 1.9.10
  • Jetpack Compose Navigation 2.7.2

Full Changelog: https://github.com/raamcosta/compose-destinations/compare/1.9.52...1.9.53

Package Rankings
Top 12.66% on Repo1.maven.org
Badges
Extracted from project README
Maven metadata URL License Apache 2.0 Android API kotlin
Related Projects