Skip to content

Releases: Fueled/flowr

FlowR 1.5.2

12 Jun 17:31
af6a4f5
Compare
Choose a tag to compare
  • Fix inconsistency issue with clear back stack.

FlowR 1.5.1

08 Jan 12:32
9bd7c16
Compare
Choose a tag to compare
chore(project): Prep for version 1.5.1

FlowR 1.5.0

13 Dec 12:40
a48f5a5
Compare
Choose a tag to compare
  • Add support for returning back to a specific fragment transaction ID, using Flowr#closeUpto(int) and Flowr#closeUptoWithResults(ResultResponse, int).

FlowR 1.4.2

10 Oct 09:50
Compare
Choose a tag to compare
  • Fix deep link handler regex pattern issue on Lollipop devices.

FlowR 1.4.1

03 Oct 15:31
Compare
Choose a tag to compare
  • Fix #32.
  • Replace FragmentManager#popBackStackImmediate with FragmentManager#popBackStack for the Flowr#clearBackStack() call. This improves performance when combing the clear back stack call with other transactions, as it remove the need to wait for the clear stack transaction to be executed before queuing the other transactions.
  • Remove the no longer needed fragment replace issue workaround, as it was fixed in support library version 25.1.0.
  • Start generating sources and java docs artifacts when building the library.
  • Update support library to version 26.1.0 and build tools to version 16.0.1.

FlowR 1.4.0

11 Jul 13:54
Compare
Choose a tag to compare
  • Observe fragment changes in FlowrScreen using onCurrentFragmentChanged(Fragment).
  • Improve nullability checks.

FlowR 1.3.1

29 Jun 15:23
Compare
Choose a tag to compare

Expose setRouterScreen in order to set the screen after the Flowr instance has already been created, specifically when using a Fragment as a FlowrScreen.

FlowR 1.3.0

06 Jun 17:50
Compare
Choose a tag to compare

Support multiple module deep links.

FlowR 1.2.3

25 May 15:32
Compare
Choose a tag to compare

Fix package computation for the deep link handler when fragment are in different package.

FlowR 1.2.2

24 May 22:19
Compare
Choose a tag to compare

Add deep link support:
First, setup the deep link as explained in the documentation.
Then annote your fragment with a @DeepLink annotation. That value will be the relative path...

@DeepLink("/path1/")
public class TestFragment extends Fragment implement FlowrFragment

... or two.

@DeepLink({"/path1/","path2"})
public class TestFragment extends Fragment implement FlowrFragment

You can also insert variable:

@DeepLink("/{id}/details")
public class TestFragment extends Fragment implement FlowrFragment
.
.
.
String url = getArguments().getString(Flowr.DEEP_LINK_URL,"");
String id = getArguments().getString("id","");

To trigger the deep linking handling, simply call open(Intent, Fragment))

getFlowr()
    .open(getIntent(), HomeFragment.class)
    .skipBackStack(true)
    .displayFragment();

Additionally you can access a Fragment via the link attached to it:

getFlowr()
    .open("/path1/")
    .skipBackStack(true)
    .displayFragment();

variables work too:

getFlowr()
    .open("/1234/details")
    .skipBackStack(true)
    .displayFragment();

But don't forget to add those lines to your proguard config:

-keep public class * implements com.fueled.flowr.internal.FlowrConfig
-keep public class * implements com.fueled.flowr.internal.FlowrDeepLinkHandler