Skip to content

AnomalyType parsing vs Anomaly #15

Description

@auriium

Anomaly parser should be platform ignorant and simply build a small message informing the user what went wrong
AnomalyType (wip) should be platform dependent, build outer messages with cool platform features like click messages, probably delegate to the new interfacing boss in #10

Order of anomaly submit is like:

(where I is an object handling the input type of the node base and a handling final adapted type)

AnomalyParser -> (if on correct platform) -> AnomalyTypeParser -> MessageBoss<I,A> -> Player
(if on incorrect platform) -> MessageBoss<I,A> -> Player

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions