Skip to content

Commit

Permalink
Merge remote-tracking branch
Browse files Browse the repository at this point in the history
'origin/Hierarchy.RecursiveHierarchyActions' into
interface/hierarchy-maintenance
  • Loading branch information
HeikoTheissen committed Jan 11, 2024
2 parents 2ae6745 + 08c0f1c commit 1cb5577
Show file tree
Hide file tree
Showing 3 changed files with 9 additions and 7 deletions.
2 changes: 1 addition & 1 deletion vocabularies/Hierarchy.json
Original file line number Diff line number Diff line change
Expand Up @@ -108,7 +108,7 @@
"RecursiveHierarchyActionsType": {
"$Kind": "ComplexType",
"@Common.Experimental": true,
"@Core.LongDescription": "The qualified action names identify actions for maintaining nodes in the recursive hierarchy,\nwhich are specific for the given annotation qualifier.\nThese binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.\nThe resource path of the binding parameter MUST traverse the hierarchy collection,\nincluding any hierarchy directory. If the resource path contains a Content ID reference to an earlier request,\nthe hierarchy directory MUST be determined from the resource path of that request.\n```json\n{\"requests\": [{\n \"id\": \"1\",\n \"method\": \"post\",\n \"url\": \"HierarchyDirectory(1)/Nodes('A')/Children\",\n \"body\": {\n \"Name\": \"child of A\"\n }\n}, {\n \"id\": \"2\",\n \"dependsOn\": [\"1\"],\n \"method\": \"post\",\n \"url\": \"$1/Hierarchy.ChangeNextSibling\",\n \"body\": {\n \"NextSibling\": null\n }\n}]}\n```",
"@Core.LongDescription": "The qualified action names identify actions for maintaining nodes in the recursive hierarchy,\nwhich are specific for the given annotation qualifier.\nThe binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.\nThe resource path of the binding parameter MUST traverse the hierarchy collection,\nincluding any hierarchy directory. If the resource path contains a Content ID reference to an earlier request,\nthe hierarchy directory MUST be determined from the resource path of that request.\n```json\n{\"requests\": [{\n \"id\": \"1\",\n \"method\": \"post\",\n \"url\": \"HierarchyDirectory(1)/Nodes('A')/Children\",\n \"body\": {\n \"Name\": \"child of A\"\n }\n}, {\n \"id\": \"2\",\n \"dependsOn\": [\"1\"],\n \"method\": \"post\",\n \"url\": \"$1/Hierarchy.ChangeNextSibling\",\n \"body\": {\n \"NextSibling\": null\n }\n}]}\n```",
"ChangeNextSiblingAction": {
"$Type": "Common.QualifiedName",
"$Nullable": true,
Expand Down
12 changes: 7 additions & 5 deletions vocabularies/Hierarchy.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,8 +17,9 @@ Term|Type|Description
## Actions

<a name="ChangeNextSibling"></a>
### [ChangeNextSibling](./Hierarchy.xml#L295:~:text=<Action%20Name="-,ChangeNextSibling,-") *([Experimental](Common.md#Experimental))*
### [*ChangeNextSibling*](./Hierarchy.xml#L295:~:text=<Action%20Name="-,ChangeNextSibling,-") *([Experimental](Common.md#Experimental))*

**Signature only:**
Move a node among its siblings

Parameter|Type|Description
Expand All @@ -28,8 +29,9 @@ Parameter|Type|Description


<a name="CopyNode"></a>
### [CopyNode](./Hierarchy.xml#L331:~:text=<Action%20Name="-,CopyNode,-") *([Experimental](Common.md#Experimental))*
### [*CopyNode*](./Hierarchy.xml#L331:~:text=<Action%20Name="-,CopyNode,-") *([Experimental](Common.md#Experimental))*

**Signature only:**
Copy a node and its descendants

To give the copied sub-hierarchy a parent, the action invocation can be followed
Expand Down Expand Up @@ -144,7 +146,7 @@ Property|Type|Description

The qualified action names identify actions for maintaining nodes in the recursive hierarchy,
which are specific for the given annotation qualifier.
These binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.
The binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.
The resource path of the binding parameter MUST traverse the hierarchy collection,
including any hierarchy directory. If the resource path contains a Content ID reference to an earlier request,
the hierarchy directory MUST be determined from the resource path of that request.
Expand All @@ -169,8 +171,8 @@ the hierarchy directory MUST be determined from the resource path of that reques

Property|Type|Description
:-------|:---|:----------
[ChangeNextSiblingAction](./Hierarchy.xml#L190:~:text=<ComplexType%20Name="-,RecursiveHierarchyActionsType,-")|[QualifiedName?](Common.md#QualifiedName)|
[CopyAction](./Hierarchy.xml#L198:~:text=<ComplexType%20Name="-,RecursiveHierarchyActionsType,-")|[QualifiedName?](Common.md#QualifiedName)|
[ChangeNextSiblingAction](./Hierarchy.xml#L190:~:text=<ComplexType%20Name="-,RecursiveHierarchyActionsType,-")|[QualifiedName?](Common.md#QualifiedName)|**Implements [ChangeNextSibling](#ChangeNextSibling)**
[CopyAction](./Hierarchy.xml#L198:~:text=<ComplexType%20Name="-,RecursiveHierarchyActionsType,-")|[QualifiedName?](Common.md#QualifiedName)|**Implements [CopyNode](#CopyNode)**

<a name="TopLevelsExpandType"></a>
## [TopLevelsExpandType](./Hierarchy.xml#L274:~:text=<ComplexType%20Name="-,TopLevelsExpandType,-") *([Experimental](Common.md#Experimental))*
Expand Down
2 changes: 1 addition & 1 deletion vocabularies/Hierarchy.xml
Original file line number Diff line number Diff line change
Expand Up @@ -164,7 +164,7 @@ the following collections of hierarchy nodes are distinguished:
<Annotation Term="Core.LongDescription">
<String>The qualified action names identify actions for maintaining nodes in the recursive hierarchy,
which are specific for the given annotation qualifier.
These binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.
The binding parameter of the actions MUST be the entity type on which the recursive hierarchy is defined.
The resource path of the binding parameter MUST traverse the hierarchy collection,
including any hierarchy directory. If the resource path contains a Content ID reference to an earlier request,
the hierarchy directory MUST be determined from the resource path of that request.
Expand Down

0 comments on commit 1cb5577

Please sign in to comment.