← Prev in month ← Prev in thread

[OASIS Issue Tracker] (ODATA-1078) What happens if lambda variable name matches a (complex) property name?

From
OASIS Issues Tracker <>
Date
2017-05-18T16:53:46+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-1078) What happens if lambda variable name matches a (complex) property name?
Michael Pizzo created ODATA-1078:
------------------------------------

             Summary: What happens if lambda variable name matches a (complex) property name?
                 Key: ODATA-1078
                 URL: https://issues.oasis-open.org/browse/ODATA-1078
             Project: OASIS Open Data Protocol (OData) TC
          Issue Type: Bug
          Components: URL Conventions
    Affects Versions: V4.01_CSD02, V4.0_ERRATA03
            Reporter: Michael Pizzo
             Fix For: V4.01_CSD02


MUST all paths wthin a lambda operator be prefixed with either a lambda variable name (potentially from an enclosing lambda operator) or $it/ to reference properties of the base set?
Or is $it/ not required for properties/paths in the base set? Which would require that the lambda operator MUST NOT be identical to any property name in the base set?
My inclination would be:
1) It is not required
2) In case of conflict, lambda variable name wins (you shouldn't pick a lambda variable name that conflicts...)



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
← Prev in month ← Prev in thread