Query optional argument includeAllowableActions doesn't make sense.

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: Domain Model
    • None
    • Hide

      Query has all the include options of getChildren. For queries where the select clause contains properties from only one virtual table reference (e.g., referenced object type), the include options MAY be used. If the include options are used, the repository MUST include the information from the object type reference whose properties are specified in the select clause. If the select clause contains properties from more than one object type reference, the repository MUST/SHOULD throw an exception.

      also clarify reference terminology in query section (e.g., define object type reference)

      Show
      Query has all the include options of getChildren. For queries where the select clause contains properties from only one virtual table reference (e.g., referenced object type), the include options MAY be used. If the include options are used, the repository MUST include the information from the object type reference whose properties are specified in the select clause. If the select clause contains properties from more than one object type reference, the repository MUST/SHOULD throw an exception. also clarify reference terminology in query section (e.g., define object type reference)

      Line 2794 - includeAllowableActions doesn't make sense as the output is not objects, but query results, and thus have no AllowableActions.

            Assignee:
            Ethan Gur-esh (Inactive)
            Reporter:
            Ryan McVeigh (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: