Skip to content

Persistence #33

@RedC4ke

Description

@RedC4ke

Hi!

We really love how your package streamlines form building, however we've encountered an issue. Sometimes we need to invoke an external intent, which makes the Android Activity susceptible to be destroyed. I've researched the built-in Flutter persistence solutions, but it seems none of them really fit in this case, especially when using multiple subforms.

It would be very appreciated to hear how you guys solve this issue in your company or to get a persistence feature added to leancode_forms, for example using hydrated_bloc.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions