Conversation
...est_api/rest_api_reference/input/examples/ai/actions/GET/ActionConfigurationList.xml.example
Outdated
Show resolved
Hide resolved
...st_api/rest_api_reference/input/examples/ai/actions/GET/ActionConfigurationList.json.example
Show resolved
Hide resolved
...pi/rest_api/rest_api_reference/input/examples/ai/actions/GET/ActionConfiguration.xml.example
Show resolved
Hide resolved
...i/rest_api/rest_api_reference/input/examples/ai/actions/GET/ActionConfiguration.json.example
Show resolved
Hide resolved
|
Preview of modified Markdown: no Markdown change to preview. |
| @@ -1,5 +1,5 @@ | |||
| displayName: AI Actions | |||
| /execute/{actionConfiguration}: | |||
| displayName: AI actions | |||
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
There was a problem hiding this comment.
(Answered in DM - the short answer is that the old route still works)
| /actions: | ||
| get: | ||
| displayName: List action configurations | ||
| description: Returns a list of action configurations |
There was a problem hiding this comment.
| description: Returns a list of action configurations | |
| description: Returns a list of action configurations. |
| description: Returns a list of action configurations | ||
| queryParameters: | ||
| limit: | ||
| description: The number of results per page |
There was a problem hiding this comment.
Seems like we are inconsistent in putting fullstops at the end of query paramater descriptions, but the ones with fullstop largely prevail.
I'd add fullstops then, even though these are not full sentences. Alternatively, we'd want to go through all descriptions and amend them to have fullstops in sentences and no fullstops in nominal sentence fragments
| type: string | ||
| text: | ||
| type: string[] | ||
| ActionTypeListWrapper: |
There was a problem hiding this comment.
Again, we are inconsistent in providing descriptions for objects and for object properties. For close to 2 thousand elements that could have a description key (objects and properties), there is a little over a thousand descriptions.
What's the convention?
|
@julitafalcondusza @dabrt full stops and descriptions added in: |
| </a> | ||
| </td> | ||
| <td></td> | ||
| <td>JSON object with only RefineText property.</td> |
There was a problem hiding this comment.
| <td>JSON object with only RefineText property.</td> | |
| <td>JSON object with only the RefineText property.</td> |
| </a> | ||
| </td> | ||
| <td></td> | ||
| <td>JSON object with only a GenerateAltText property.</td> |
There was a problem hiding this comment.
| <td>JSON object with only a GenerateAltText property.</td> | |
| <td>JSON object with only the GenerateAltText property.</td> |
| </a> | ||
| </td> | ||
| <td></td> | ||
| <td>JSON object with only AltText property.</td> |
There was a problem hiding this comment.
| <td>JSON object with only AltText property.</td> | |
| <td>JSON object with only the AltText property.</td> |
| </a> | ||
| </td> | ||
| <td></td> | ||
| <td>JSON object with only RefineText property.</td> |
There was a problem hiding this comment.
| <td>JSON object with only RefineText property.</td> | |
| <td>JSON object with only the RefineText property.</td> |
| </a> | ||
| </td> | ||
| <td></td> | ||
| <td>JSON object with only ActionTypeList property.</td> |
There was a problem hiding this comment.
| <td>JSON object with only ActionTypeList property.</td> | |
| <td>JSON object with only the ActionTypeList property.</td> |
| - | ||
| <span> | ||
| </span> | ||
| JSON object with only RefineText property.</span> |
There was a problem hiding this comment.
| JSON object with only RefineText property.</span> | |
| JSON object with only the RefineText property.</span> |
| - | ||
| <span> | ||
| </span> | ||
| JSON object with only RefineText property.</span> |
There was a problem hiding this comment.
| JSON object with only RefineText property.</span> | |
| JSON object with only the RefineText property.</span> |
| - | ||
| <span> | ||
| </span> | ||
| JSON object with only AltText property.</span> |
There was a problem hiding this comment.
| JSON object with only AltText property.</span> | |
| JSON object with only the AltText property.</span> |
| - | ||
| <span> | ||
| </span> | ||
| JSON object with only ActionTypeList property.</span> |
There was a problem hiding this comment.
| JSON object with only ActionTypeList property.</span> | |
| JSON object with only the ActionTypeList property.</span> |
| - | ||
| <span> | ||
| </span> | ||
| Object describing the criteria used to search for Action Conigurations.</span> |
There was a problem hiding this comment.
| Object describing the criteria used to search for Action Conigurations.</span> | |
| Object describing the criteria used to search for Action Configurations.</span> |
* [REST] New AI endpoints * Review fixes - part 1 * Regenerated responses * Rebuild the reference * Added fullstops. * Added descriptions * Regemerated the reference * Description fixes * Regenerated the reference
Doc for endpoints introduced in:
Preview
Questions:
GET /ai/actionsandPOST /ai/actionsreturn the same data - I wasn't sure how to name these entries, I've chosen:but maybe there's something better