Improve function & function parameter select strategy
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 505
- Forks
- 186
- PR merge metrics
- No merged PRs in 30d
Description
In current implementation, we consider that:
if function parameters defined in Edm function shows in the action, we consider the action is the candidate.
However, we should improve it to that:
Except the known parameters, for example (CancellationToken, ODataQueryOption, ODataQueryOptions, ODataPath, etc), we should exactly match the remaining parameters with the Edm function parameters.
Contributor guide
No contributing guide indexed for this repository
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 by locating the function and action selection entry point, then inspect how known parameters such as CancellationToken, ODataQueryOption, ODataQueryOptions, and ODataPath are excluded. Done means candidate selection exactly matches the remaining action parameters with the Edm function parameters.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend-api-design
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100