automaton-simulation-de.response

Liking cljdoc? Tell your friends :D

All platforms.

add-current-event-to-stopping-causes
add-stopping-cause
build
consume-first-event
schema
validate

Is a response of scheduler.

It contains:

stopping-causes
snapshot.

Is a response of scheduler.

It contains:
* `stopping-causes`
* `snapshot`.

raw docstring

add-current-event-to-stopping-causes^clj/s

(add-current-event-to-stopping-causes response current-event)

Adds current-event to stopping-causes in the response.

Adds `current-event` to `stopping-causes` in the `response`.

raw docstring

add-stopping-cause^clj/s

(add-stopping-cause response m)

Adds map m among stop-causes.

Adds map `m` among `stop-causes`.

raw docstring

build^clj/s

(build stopping-causes snapshot)

Creates a response with the stopping-causes and snapshot.

Creates a response with the `stopping-causes` and `snapshot`.

raw docstring

consume-first-event^clj/s

(consume-first-event {:automaton-simulation-de.response/keys [snapshot]
                      :as response}
                     current-event)

Moves the response to the next operation. current-event is added to the stopping-cause if causality is broken. Consists in:

removing the first event in the future-events and push it in past-event.
adding :causality-broken stopping-cause if that event is coming back to the past. Note that in case causality is broken, the date is not modified and keep the previous snapshot date instead of the faulty event date.

Moves the `response` to the next operation. `current-event` is added to the `stopping-cause` if causality is broken.
Consists in:

* removing the first event in the `future-events` and push it in `past-event`.
* adding `:causality-broken` `stopping-cause` if that event is coming back to the past.
Note that in case causality is broken, the date is not modified and keep the previous snapshot date instead of the faulty event date.

raw docstring