ek9_add_to_sealed_allowlist

Rewrites the sealed type's 'allow only' line with the new subtypes appended; answers status, edits[] and summary, each bad entry as conflicts[] (target-not-sealed, entry-does-not-extend-target, entry-already-in-allowlist).

Category: Editor · Compare: Kotlin sealed-hierarchy extension (loose analogue)

When to use it

'Let Pentagon and Hexagon into sealed Shape' is one call with symbol:'Shape' and allowOnly:['Pentagon','Hexagon'] - every unlisted subtype at once, no line.

When not to use it

Target is NOT yet sealed (no 'allow only' clause) - use ek9_seal_type for the initial seal; it writes the whole list.
Removing the seal entirely rather than extending the list - use ek9_unseal_type.
The entry does not yet extend/implement the target - add the extends / with trait of clause to the entry's class first (else 'entry-does-not-extend-target'), then re-call.
The entry is abstract, or a dispatcher over the target lacks a handler for it - ek9_make_concrete / ek9_generate_dispatcher / ek9_add_method first (else post-apply E05250 / E05260 would-fail).

Details

conflicts kinds (all bad entries reported at once, not just the first): 'target-not-sealed' (mechanical - switch to ek9_seal_type), 'entry-does-not-extend-target' (escalation - add extends / with trait of first), 'entry-already-in-allowlist' (mechanical no-op - drop it from allowOnly). Abstract entry (E05250) and dispatcher-non-exhaustive (E05260) are NOT pre-checked - they surface as would-fail. Entries de-duplicated, appended in the order given; the typical baseline is already E05240-errored, and since apply verifies only NEW diagnostics, clearing it yields 'applied'.

Arguments

Argument	Type	Required	What it is
`allowOnly`	array of string	yes	Concrete subtype names to add to the target's 'allow only' list, appended in the order given. Pass every unlisted subtype you intend to permit.
`file`	string		The EK9 source file - OPTIONAL when symbol is a construct name; required to anchor on a member or a use site.
`line`	integer		1-based line of the declaration or a reference - OMIT it and pass symbol:'<name>' to let the tool find the line (a model counting lines in a file miscounts); if you do count, use `ek9_read_file`(lineNumbers:true).
`symbol`	string	yes	The sealed class or trait - a bare name ('Shape') finds its file and declaration workspace-wide; 'mod::Shape' when the name is declared in two modules.

It also takes the arguments every tool takes.

Recorded calls

Real calls, recorded against small projects and checked on every build - a changed answer fails it. 3 of the 7 recorded are shown.

Add to sealed allowlist already in allowlist

Request

{
  "entries" : [ "Circle" ],
  "file" : "shapes.ek9",
  "line" : 6
}

Response

{
  "conflicts" : [ {
    "entry" : "Circle",
    "kind" : "entry-already-in-allowlist",
    "message" : "Circle is already permitted — nothing to add"
  } ],
  "edits" : [ ],
  "meta" : {
    "serverMs" : "<timing>"
  },
  "risk" : {
    "crossesModuleBoundary" : false,
    "estimatedSeverity" : "trivial",
    "fileCount" : 0,
    "lineCount" : 0,
    "touchesPublicApi" : false,
    "touchesTests" : false
  },
  "status" : "conflicts",
  "summary" : "Circle cannot be added to Shape's allow only list",
  "workspaceHash" : "<workspace-hash>",
  "wouldBeDiagnostics" : [ ],
  "written" : false
}

Add to sealed allowlist target not sealed

Request

{
  "entries" : [ "Circle" ],
  "file" : "shapes.ek9",
  "line" : 6
}

Response

{
  "conflicts" : [ {
    "hint" : "seal the type first with ek9_seal_type (which writes the full allow only list)",
    "kind" : "target-not-sealed"
  } ],
  "edits" : [ ],
  "meta" : {
    "serverMs" : "<timing>"
  },
  "risk" : {
    "crossesModuleBoundary" : false,
    "estimatedSeverity" : "trivial",
    "fileCount" : 0,
    "lineCount" : 0,
    "touchesPublicApi" : false,
    "touchesTests" : false
  },
  "status" : "conflicts",
  "summary" : "Shape is not sealed — use ek9_seal_type for initial sealing",
  "workspaceHash" : "<workspace-hash>",
  "wouldBeDiagnostics" : [ ],
  "written" : false
}

Add to sealed allowlist apply

Request

{
  "entries" : [ "Triangle" ],
  "file" : "shapes.ek9",
  "line" : 6
}

Response

{
  "conflicts" : [ ],
  "edits" : [ {
    "after" : "    Shape allow only Circle, Square, Triangle",
    "before" : "    Shape allow only Circle, Square",
    "endLine" : 6,
    "file" : "shapes.ek9",
    "startLine" : 6,
    "type" : "replace"
  } ],
  "meta" : {
    "serverMs" : "<timing>"
  },
  "risk" : {
    "crossesModuleBoundary" : false,
    "estimatedSeverity" : "trivial",
    "fileCount" : 1,
    "lineCount" : 1,
    "touchesPublicApi" : false,
    "touchesTests" : false
  },
  "status" : "applied",
  "summary" : "Changed Added Triangle to Shape allow only list",
  "workspaceHash" : "<workspace-hash>",
...

Cut short here: 3 more lines. The whole recorded call.

When to use it

When not to use it

Details

Arguments

Recorded calls

Add to sealed allowlist already in allowlist

Add to sealed allowlist target not sealed

Add to sealed allowlist apply

See also