انتقل إلى المحتوى الرئيسي

Variable: SETUP_STEPS

const SETUP_STEPS: object

Defined in: packages/contracts/src/setup.ts:108

Which answer-file sections each step may write, and nothing else about a step that the console must not guess. A section sent to a step that does not list it is refused (section_not_in_step): the anchor's name is not changed from the identity provider's screen. Listed in SETUP_STEP_IDS order.

The anchor section has two halves, written by two steps. Its name and slug are the anchor organisation's and are written with organizations (the wizard's screen 3, which applies that step only); its public facts (contacts, disputeRoute, frameworkDocument) found the trust tree and are written with anchor (screen 10), after identifiers has published the identifier the framework is named by. A section is the unit here, so both steps list it; what keeps the halves apart is that a finished step is read-only down to the JSON pointers it reads (step_done), and organizations reads the name and slug and nothing of the public facts.

Type Declaration​

accounts​

readonly accounts: object

accounts.sections​

readonly sections: readonly ["governingAccount"]

anchor​

readonly anchor: object

anchor.sections​

readonly sections: readonly ["anchor", "governance"]

configuration​

readonly configuration: object

configuration.sections​

readonly sections: readonly [] = []

identifiers​

readonly identifiers: object

identifiers.sections​

readonly sections: readonly ["identifiers"]

identity-provider​

readonly identity-provider: object

identity-provider.sections​

readonly sections: readonly ["identityProvider", "rootAccount", "machineClients"]

key-store​

readonly key-store: object

key-store.sections​

readonly sections: readonly [] = []

organizations​

readonly organizations: object

organizations.sections​

readonly sections: readonly ["deployment", "anchor", "organizations"]