Rulealize Registry Find a name /

Rule sets / Minesweeper

rule set

Rulealize.RuleSet.Minesweeper

Minesweeper on a 9 × 9 board with ten mines, laid after the first cell is opened and never next to it. A Rulealize rule set.

What 1.0.0 is made of

this documentMinesweeper1.0.0
requires — this document's owntypeRulealize.Plugin.TypeSchema^1.0stateRulealize.Plugin.State^1.0seqRulealize.Plugin.Sequence^1.2cmpRulealize.Plugin.Comparison^1.0logicRulealize.Plugin.Logic^1.0mathRulealize.Plugin.Arithmetic^1.0branchRulealize.Plugin.Branch^1.0bindRulealize.Plugin.Binding^1.0defRulealize.Plugin.Definition^1.0gridRulealize.Plugin.Grid^1.1graphRulealize.Plugin.Graph^1.0chanceRulealize.Plugin.Chance^1.1

Hold it

A document that holds this one writes, in its uses:

"uses": [
  { "ruleSet": "Rulealize.RuleSet.Minesweeper",
    "version": "^1.0", "as": "minesweeper" }
]

as is not optional here. The identifier is the package identifier, so nothing has to look it up; as is the short name the holding document calls it by, and it is what qualifies this rule set's inputs inside that one. An alias defaults to the identifier and may not contain a ., so leaving it out is refused with a message about a key you did not write.

Getting what a uses names is the feed's job rather than this index's. rulealize restore does it from 0.8.0 — the whole graph, into the folder the holding document resolves its components from — and takes the lowest version satisfying every constraint that named it, which is the rule a requires is resolved by.

Inputs a composite could constrain

InputComes from
digsthis document
flagsthis document
tapthis document

Releases

  1. 1.0.0 latest

    requires

    inputs

    • digs
    • flags
    • tap