All Versions
10
Latest Version
Avg Release Cycle
73 days
Latest Release
845 days ago

Changelog History

  • v3.3.0 Changes

    June 25, 2019

    #208
    โž• ADDED: FragNavTransactionOptions.allowReordering(reorder: Boolean)

  • v3.2.0 Changes

    March 18, 2019

    #204

    • Trigger transaction listener when restoring tab from bundle #201
    • โšก๏ธ Update AndroidX dependencies
  • v3.1.0 Changes

    December 26, 2018
    • Ability to clear a stack other than the one you are currently on #172
    • Migrate to AndroidX #161
    • ๐Ÿ›  Fix pop animation #176
    • โœ… General improvements and tests added
  • v3.0.0 Changes

    November 19, 2018

    ๐Ÿš€ Major release.
    The library has been transitioned to Kotlin.

    ๐Ÿ— The builder has been entirely removed. This allows for creating a Non-Nullable val object of the FragNavController, as the only things required for initializing the controller are the Container (this should never change) and the fragmentManager (ditto). Everything else can be set as pleased and will be correctly initialized using the initialize function. The secondary benefit to this is that if you are using a single Activity, and need to change the tab structure, you can set things on the fly and just call the initialize function when needed.

    โšก๏ธ Please refer to the sample app for suggested best practices, and I will be updating the readme as well as taking feedback over the next couple weeks.

  • v3.0.0-RC Changes

    April 22, 2018

    ๐Ÿš€ This is a pre-release in order to get some in field testing. Since this is a major re-write, I want to give a week or two of usage, bug fixing, feedback before going live with a production ready release.

    ๐Ÿš€ This is a Major point release, meaning it has breaking changes.

    โšก๏ธ The library has been completed transitioned over to Kotlin, but with the intention of having it as easy to use as possible on either Java or Kotlin. That being said, some heavy underlying changes were made in order to optimize things for Kotlin (without making any sacrifices on the Java end)

    ๐Ÿ— The builder has been entirely removed. This allows for creating a Non-Nullable val object of the FragNavController, as the only things required for initializing the controller are the Container (this should never change) and the fragmentManager (ditto). Everything else can be set as pleased and will be correctly initialized using the initialize function. The secondary benefit to this is that if you are using a single Activity, and need to change the tab structure, you can set things on the fly and just call the initialize function when needed.

    โšก๏ธ Please refer to the sample app for suggested best practices, and I will be updating the readme as well as taking feedback over the next couple weeks.

  • v2.4.0 Changes

    November 21, 2017
    • โœ‚ removed executePendingTransactions from being called after every commit, and instead made the function public and open for the consumer to decide when it is needed
    • โž• added 3 navigation strategies via #98 Thanks @mateherber !
  • v2.3.0 Changes

    November 16, 2017
    • Modified how public Fragment getCurrentFrag() works. There were previously situations where a fragment had been transacted, and thus was on the stack, but the function was still returning the previous function. This should no longer be the case.
    • Made void initialize(@TabIndex int index) a public function. This can be useful if you want to clear all the stacks and start over.
  • v2.2.3 Changes

    October 09, 2017
    • โšก๏ธ updated build tools, support libraries
    • โฌ‡๏ธ reduced dependencies #91
  • v2.2.2 Changes

    September 19, 2017
    • ๐Ÿ›  Fixed restoring from stateLoss by making sure the defaultTransactionOptions aren't used #88
  • v2.2.1 Changes

    September 09, 2017
    • โž• added boolean isStateSaved() function to check if the FragmentManager is in a saved state. This is useful to know before hand so you can decide to allowStateLoss