When you set up a new OData endpoint, you typically have to register a bunch of settings to turn OData features on, like this:
endpoints.Select().Expand().Filter().OrderBy().MaxTop(100).Count().SetTimeZoneInfo(TimeZoneInfo.Utc);
But you can also register ODataValidationSettings to control some elements of that process, like this:
services.AddSingleton(new ODataValidationSettings
{
MaxTop = 5,
MaxAnyAllExpressionDepth = 3,
MaxExpansionDepth = 3,
});OData does not check if these settings are in conflict, and it's not clear which settings will take priority.
Restier 2.0 should make it easier to control expansion depth without creating MaxTop conflicts. It should warn you if you hack the system to create conflicts anyway, and those warnings should be clear about what settings were applied in what order.
Should fix:
When you set up a new OData endpoint, you typically have to register a bunch of settings to turn OData features on, like this:
But you can also register
ODataValidationSettingsto control some elements of that process, like this:OData does not check if these settings are in conflict, and it's not clear which settings will take priority.
Restier 2.0 should make it easier to control expansion depth without creating MaxTop conflicts. It should warn you if you hack the system to create conflicts anyway, and those warnings should be clear about what settings were applied in what order.
Should fix:
MaxTopdoesn't change the limit forTop#719