Skip to content

Handling error states #15

Description

@g105b

If a form submits and the response doesn't match the expected HTML structure, Flux won't be able to replace the correct elements.

Currently, this fails silently.

Instead, I want to implement a failure state - if any flux update element can't update itself, Flux should fall back to a normal full-page response. It can't do this by submitting the form again, otherwise the form will be handled twice on the server, but it can replace the entire <html> element.

A special full-page replacement (with history push) should be introduced for handling errors.

404, 500, etc. should be handled normally, without any change, unless the page structure doesn't match.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    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