OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-1633) In should support empty literal arrays


Michael Pizzo created ODATA-1633:
------------------------------------

             Summary: In should support empty literal arrays
                 Key: ODATA-1633
                 URL: https://issues.oasis-open.org/browse/ODATA-1633
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: New Feature
          Components: ABNF
    Affects Versions: V4.01_OS
         Environment: [Proposed]
            Reporter: Michael Pizzo
             Fix For: V4.02


[ABNF] defines the inexpr as:

inExpr = RWS "in" RWS ( listExpr / commonExpr )

where listExpr is defined as:

listExpr  = OPEN BWS primitiveLiteral BWS *( COMMA BWS primitiveLiteral BWS ) CLOSE

meaning, the list must have at least one primitive literal.

Client code generating the expression may well write the open paren, loop through the elements of the array writing each into the expression, then write a close paren.  If the array is empty, this will result in an empty listExpr.

Any reason not to allow an empty listExpr and force the client code above to handle this as a special case?



--
This message was sent by Atlassian Jira
(v8.3.3#803004)


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]