Has there been any mention of dealing with orientation changes and state persistence? I see JetNews ...

# compose

[Ian Warwick]

Has there been any mention of dealing with orientation changes and state persistence? I see JetNews uses global variables to store state and wonder if this is the proposed solution or one that JetNews just took (which is feasible of course) or if there is some way to init state and persist it as long as the current activity including config changes like view models do?

[Zsolt]

State persistence is manageable with ambient Bundles hooked into root Activity, though I'm not sure if this is right or wrong. You can check https://github.com/zsoltk/compose-router for an example.

[Ian Warwick]

Ah cool, I was told in another thread that ambients are equivalent to service locator,

[Ian Warwick]

am doing something very similar in my playground app though with URI based routing (because where I work we like deep linking!) 😆

[Zsolt]

Yeah, I've seen it. It's possible to add URI matching to the above too. One benefit would be compile-time safety with sealed classes vs strings, and to not allow just any random URI but have some control over what's allowed.

[Ian Warwick]

Yep this is true

[Ian Warwick]

Instead of using String, Uri would ensure valid URI's though I don't like it, for strong typedness definetly sealed classes are the way to go, something for me to think about thanks! 🙂

[Paul Woitaschek]

Afaik uri doesn't validate anything

[Paul Woitaschek]

public static Uri parse(String uriString) {
        return new StringUri(uriString);
    }

[Paul Woitaschek]

`

private StringUri(String uriString) {
    if (uriString == null) {
        throw new NullPointerException("uriString");
    }

    this.uriString = uriString;
}

[Paul Woitaschek]

So it only validates that you don't pass null

[Ian Warwick]

ah interesting I always thought it was validated to be correct though sounds like I was wrong

[Paul Woitaschek]

Of cause you thought so

[Paul Woitaschek]

`

/**
 * Creates a Uri which parses the given encoded URI string.
 *
 * @param uriString an RFC 2396-compliant, encoded URI
 * @throws NullPointerException if uriString is null
 * @return Uri for this given uri string
 */

[Paul Woitaschek]

This really implies that it's validating

[Ian Warwick]

cool thanks for clarifying I tried it and yes anything parses fine Uri.parse("abc")! 😆

[shikasd]

I am actually not quite sure that it will validate anything logically.
E.g. if you want to open gallery in user info screen, you could do /user/1/gallery as a route, meaning you have gallery in user screen.

However, you can do /user/1/not-gallery , it will pass validation, but will be logically incorrect, as you don't have not-gallery in user screen.

[Zsolt]

Updated compose-router with a proof-of-concept impl of deep link uri based routing. See repo / bottom of main README for two examples. The mechanism separates the URI and the actual routing in that it doesn't have direct control over what happens. It's first matched / parsed / validated, then mapped to elements of Routing sealed classes.