search

auriium / Branch

Advanced, powerful, verbose yet concise conceptual execution-node command framework
1 stars 1 forks source link

AnomalyType parsing vs Anomaly #15

Open auriium opened 3 years ago

auriium commented 3 years ago

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

auriium commented 3 years ago

This is wrong, it should be

Anomaly -> AnomalyTypeParser -> (correct) -> AnomalyParser -> MessageBoss -> (incorrect) -> MessageBoss