| Key: |
CMIS-124
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Trivial
|
| Assignee: |
Unassigned
|
| Reporter: |
Ethan Gur-esh
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
| Proposal: |
Update CMIS Query Type so it's consistent with the method naming other methods use.
|
| Resolution: |
Proposal accepted -- we'll use the same names already in the domain model (e.g. maxItems, includeAllowableActions).
|
|
In the CMIS domain model/scehams, there are some general conventions around naming of common params that most methods follow:
- For paging:
-- maxItems: The page size
-- SkipCount: The # of items to skip before returning items
For allowable actions:
-- includeAllowableActions: Whether or not to return the allowable actions for each object returned.
But the cmisQueryType object defined in the schemas is inconsistent.
Instead of maxItems it uses "pageSize".
Instead of includeAllowableActions, it uses "returnAllowableActions".
|
|
Description
|
In the CMIS domain model/scehams, there are some general conventions around naming of common params that most methods follow:
- For paging:
-- maxItems: The page size
-- SkipCount: The # of items to skip before returning items
For allowable actions:
-- includeAllowableActions: Whether or not to return the allowable actions for each object returned.
But the cmisQueryType object defined in the schemas is inconsistent.
Instead of maxItems it uses "pageSize".
Instead of includeAllowableActions, it uses "returnAllowableActions". |
Show » |
|
cmisQueryType -- rename some params to be consistent with other method terminology