This implementation is a cleaned up version of the original package.

It has a few breaking changes so it is best to ensure it is fully compatible before upgrading.

We now need to specify a Stack in conjunction with the Routes.

This allows us to have all the stacks and routes in a single dictionary. Then we can store it in memory, JSON, or with your own custom persistence implementation. Previous versions were a bit too murky in their implementation APIs.

I have also made clearer uses of the replacement of stacks and routes if we need to from an network call, push notification, or other special condition.

Lastly, I have added logging to the framework to help in debugging.

What's Changed

• 2025-02-05 - Major fixes by @markbattistella in #1

New Contributors

• @markbattistella made their first contribution in #1

Full Changelog: 2.1.0...3.0.0