Extracts the endpoints namespace (#543 phase 3): the name of every
route sts_metadata.ts's ENDPOINTS describes, keyed by its path, and
the names of the socket rows this file builds.
sts_metadata is required HERE, when the namespace is first extracted
— after the stack is up — and never at load, for the reason in the
header. A name is left out when it is one word, when it is in
UNTRANSLATED_NAMES, or when it is also a protocol card's name, an
endpoint group or a specification's name: those are join keys, and on
every route a translated one would no longer join.
The name of a route repeated per named authorization server, <name> — <id>, is translated only as far as the whole string is a name: a
template {{name}} — {{server}} would match any sentence on any page
with a dash in it.
Extracts the endpoints namespace (#543 phase 3): the name of every route
sts_metadata.ts'sENDPOINTSdescribes, keyed by its path, and the names of the socket rows this file builds.sts_metadatais required HERE, when the namespace is first extracted — after the stack is up — and never at load, for the reason in the header. A name is left out when it is one word, when it is inUNTRANSLATED_NAMES, or when it is also a protocol card's name, an endpoint group or a specification's name: those are join keys, and on every route a translated one would no longer join.The name of a route repeated per named authorization server,
<name> — <id>, is translated only as far as the whole string is a name: a template{{name}} — {{server}}would match any sentence on any page with a dash in it.