These are chat archives for jdubray/sam
okay, this is a quote from jdubary:
nap is outside the step itself, the step is Action->Model->State representatio. nap represents "automatic actions", i.e. given a state/status of the system an action is expected to occur. The reality is you might find that you want to order the next action(s) and rendering could logically happen between two next actions. I prefer the automatic actions to happen afterwards because I put a bit of JQuery code (data picker initialization) in the nap().
nap()acknowledges that there are states in a program that are valid but transient.
nap()helps push the program towards a more stable/permanent state.
@jdubray thanks :relaxed:
one practical issue i can imagine implementing
nap() is avoiding infinite loops...
nap()calls an action without any insights as to whether or not the next step will cause the same next-action again.