[OASIS Issue Tracker] (ODATA-834) Make type prefix optional for enumeration literals in URLs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

     [ https://issues.oasis-open.org/browse/ODATA-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Pizzo updated ODATA-834:
--------------------------------

    Proposal: 
4.01 Services MUST support Implicit cast from string to enum in URL. This allows the use of the string value of the enum in place of the full value, as in:
$filter=Color eq 'Yellow' in addition to the existing $filter=Color eq ns.Color'Yellow'.


  was:
Allow omitting the type prefix, making e.g. these two conditions equivalent

ColorEnumValue eq Sales.Pattern'Yellow'
ColorEnumValue eq 'Yellow'



> Make type prefix optional for enumeration literals in URLs
> ----------------------------------------------------------
>
>                 Key: ODATA-834
>                 URL: https://issues.oasis-open.org/browse/ODATA-834
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData URL Conventions
>    Affects Versions: V4.0_ERRATA02
>         Environment: Simplified Syntax;[Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> Enumeration literals are represented as strings in JSON responses. Requiring the type name as a prefix in $filter expressions is a barrier for service exploration.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)