Reading diagrams / Topic 9 of 42
What an arrow does not say
The rule
An arrow is a fact about names: one package names something from another. It is not a fact about what runs.
Two things break the link. A package can import a function and never call it on the path a request takes. And a function can be handed to a package as a value, so code from a package it never imports runs inside it.
Some statements are about properties the layers lens has no field for at all: the order code runs in, how important a package is, whether code is correct, and what the program is for. Package names hint at purpose, but names are not evidence: a package called Server can do anything.
In a review, a can't tell is a question to ask, of the author or of another picture, not a pass. Later lessons show pictures that answer some of these.
- For all of these the diagram can't tell, whatever the program does.
- “Can't tell” is not a weaker yes. It means the picture holds no evidence either way.
The same Koa program. Server builds the app from middleware, and Router’s routes is one of them.
Loading the layer diagram.
The Redux program again.
Loading the layer diagram.
How to read this: what each mark in these pictures means
Loading the worked examples and practice.