Worth noting that I made a breaking API change to the startNavigation method as well. It now matches the Kotlin interface. It arguably isn't as Swifty, but I think this is probably a better API than accepting half a dozen parameters in 6 months. Moving the config to a separate object which can change, evolve new convenience initializers, etc. seems better.
Worth noting that I made a breaking API change to the
startNavigationmethod as well. It now matches the Kotlin interface. It arguably isn't as Swifty, but I think this is probably a better API than accepting half a dozen parameters in 6 months. Moving the config to a separate object which can change, evolve new convenience initializers, etc. seems better.Also closes #60 and closes #58