Microsoft.AspNetCore.OData.Routing.Template Namespace
Important
Some information relates to prerelease product that may be substantially modified before it’s released. Microsoft makes no warranties, express or implied, with respect to the information provided here.
Classes
ActionImportSegmentTemplate |
Represents a template that could match an IEdmActionImport. |
ActionSegmentTemplate |
Represents a template that could match an IEdmAction. |
CastSegmentTemplate |
Represents a template that could match a type cast segment. |
CountSegmentTemplate |
Represents a template that could match a $count segment. |
DynamicSegmentTemplate |
Represents a template that can match a DynamicPathSegment. Be noted: a dynamic path segment is a real segment (not a template), its literal is dynamic property name. |
EntitySetSegmentTemplate |
Represents a template that could match an IEdmEntitySet. |
FunctionImportSegmentTemplate |
Represents a template that could match an IEdmFunctionImport. |
FunctionSegmentTemplate |
Represents a template that could match a bound IEdmFunction. |
KeySegmentTemplate |
Represents a template that could match a key segment. |
MetadataSegmentTemplate |
Represents a template that could match "$metadata". |
NavigationLinkSegmentTemplate |
Represents a template that can match a NavigationPropertyLinkSegment and a potential key. |
NavigationLinkTemplateSegmentTemplate |
Represents a template that could match a $ref on a generic navigation segment. |
NavigationSegmentTemplate |
Represents a template that could match an IEdmNavigationProperty. |
ODataPathTemplate |
Represents a path template that could contains a list of ODataSegmentTemplate. |
ODataSegmentTemplate |
Base class for OData segment template |
ODataTemplateTranslateContext |
The context used to generate the ODataPathSegment. |
PathTemplateSegmentTemplate |
Represents a template that can match a PathTemplateSegment. From OData Lib: If template parseing enabled, any literal wrappered with "{" and "}" is considered as PathTemplateSegment. So, here's the design (so far, we can add more later): {property} ==> declared property {dynamicproperty} => dynamic property TODO: we can change to use route constraint, for example: {name:odataproperty} {name:odatadynamic} {name:odatacast} {name:odataentityset} ... |
PropertyCatchAllSegmentTemplate |
Represents a template that could match '{property}' segment. |
PropertySegmentTemplate |
Represents a template that could match an IEdmStructuralProperty. |
SingletonSegmentTemplate |
Represents a template that could match an IEdmSingleton. |
ValueSegmentTemplate |
Represents a template that could match a "/$value" segment. |
Interfaces
IODataTemplateTranslator |
Defines a contract used to translate the OData path template to OData path. |