-
Type: Improvement
-
Status: Closed
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: V4.0_CSD01
-
Fix Version/s: V4.0_CSD02
-
Component/s: ABNF, Protocol, URL Conventions
-
Labels:None
-
Environment:
[Applied]
-
Proposal:
-
Resolution:
The current definition of substringof takes first the string being searched for, and second the string being searched in.
This is widely held to be the wrong order, especially since other string functions generally take the string as the first argument.
This issue has long been a source of confusion in OData, made worse by the fact that the documentation often disagreed with the examples, and the documentation has changed several times.
To prevent any confusion with legacy, I propose we retire the "substringof" function all together and replace it with "contains" with the argument in the more intuitive order (sourcestring, searchtext)