Support for bound actions and functions on non-entity types
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 22
- Forks
- 24
- PR merge metrics
- No merged PRs in 30d
Description
Per specs it seems that bound functions (and actions?) can be used for complex and primitive types, and their collections.
boundOperation = "/" ( boundActionCall
/ boundEntityColFunctionCall [ collectionNavigation ]
/ boundEntityFunctionCall [ singleNavigation ]
/ boundComplexColFunctionCall [ complexColPath ]
/ boundComplexFunctionCall [ complexPath ]
/ boundPrimitiveColFunctionCall [ primitiveColPath ]
/ boundPrimitiveFunctionCall [ primitivePath ]
/ boundFunctionCallNoParens [ querySegment ]
)
But the model builder seemingly supports only bound functions and actions on entities and entity collections.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the OData specification and inspect EntityTypeConfigurationOfTEntityType.cs and EntityCollectionConfigurationOfTEntityType.cs, the two model-builder entry points mentioned in the issue. Trace how bound functions and actions are configured for entities and collections, then identify the corresponding coverage needed for complex, primitive, and collection types. Done means the model builder supports the specified non-entity bindings with tests demonstrating them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100