orderby enum should not contain complex types OR should project sub-properties that are not complex types #613
Description
for GET /me/calendar/events we currently project an enum value of start and start desc.
This ends up failing on the service because the start property is a complex type and cannot be used for ordering.
The conversion library should either:
- not project properties that are complex/entity types
- project sub properties of the complex/entity types which are themselves scalar types (e.g.
start/dateTime desc)
If we go with 2, this brings a couple of questions:
- how many levels of depths should this support?
- what's going to happen for consumers using that metadata to project enums / union types of constants which all of a sudden will see a / character appear, which is reserved in most programing languages?
This also impacts graph explorer as we're suggesting customers things that cannot work.
Reactions are currently unavailable