Allow bound functions after stream properties in expressions

    • Type: Bug
    • Resolution: Fixed
    • Priority: Minor
    • V4.0_ERRATA01
    • Affects Version/s: V4.0_OS
    • Component/s: ABNF
    • None
    • Environment:

      [Proposed][Applied]

    • Hide

      Change last line of rule propertyPathExpr to match case for primitiveProperty

      propertyPathExpr = ( entityColNavigationProperty [ collectionNavigationExpr ]
      / entityNavigationProperty [ singleNavigationExpr ]
      / complexColProperty [ collectionPathExpr ]
      / complexProperty [ complexPathExpr ]
      / primitiveColProperty [ collectionPathExpr ]
      / primitiveProperty [ singlePathExpr ]
      + / streamProperty [ singlePathExpr ]

      • / streamProperty
        )
      Show
      Change last line of rule propertyPathExpr to match case for primitiveProperty propertyPathExpr = ( entityColNavigationProperty [ collectionNavigationExpr ] / entityNavigationProperty [ singleNavigationExpr ] / complexColProperty [ collectionPathExpr ] / complexProperty [ complexPathExpr ] / primitiveColProperty [ collectionPathExpr ] / primitiveProperty [ singlePathExpr ] + / streamProperty [ singlePathExpr ] / streamProperty )
    • Show
      https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=598 https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=598

      We allow arbitrary property resource paths to be followed by bound actions and functions, but forgot to allow bound function segments in query expressions in the ABNF.

            Assignee:
            handl
            Reporter:
            handl
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: