Interface: PatchSortFeatureRename
@kortexya/reasoninglayer / PatchSortFeatureRename
Interface: PatchSortFeatureRename
Section titled “Interface: PatchSortFeatureRename”Defined in: src/types/sorts.ts:1699
Rename one feature declaration on a sort, and optionally move the terms’ values with it.
Remarks
Section titled “Remarks”One body states ONE edit: this rename, or a PatchSortFeatureAmendment. The engine refuses a body that combines them with 400, so the description and index keys are not allowed here.
Properties
Section titled “Properties”cascadeTerms?
Section titled “cascadeTerms?”
optionalcascadeTerms?:boolean
Defined in: src/types/sorts.ts:1716
Also rewrite the feature on every term of this sort and its subsorts.
Off by default: a schema edit is not a data migration, and under the open world the terms stay well-sorted either way. Turn it on when the declaration and the values are meant to stay one thing — SortFeatureEditResponse.termsUpdated then says how many moved.
description?
Section titled “description?”
optionaldescription?:undefined
Defined in: src/types/sorts.ts:1718
Not allowed on a rename: amend the description in a separate call.
index?
Section titled “index?”
optionalindex?:undefined
Defined in: src/types/sorts.ts:1720
Not allowed on a rename: amend the index directive in a separate call.
name:
string
Defined in: src/types/sorts.ts:1707
The name the declaration takes.
Held to the OSFQL identifier rule in the feature_name position, which
admits no dot. Refused when the sort, or a subsort that inherits the
declaration, already declares it.