microsoft / microsoft/Power-Fx
Resolve use of KeyNotFoundException in OData case
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.4k
- Forks
- 358
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 3
Description
Change #507 introduces a catch (KeyNotFoundException) for the Odata support in ODataVisitor.cs. (search that PR for this issue number for context).
We should have a cleaner way to handle this.
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
Review PR #507 for the context around this issue, then inspect ODataVisitor.cs and its KeyNotFoundException handling. Determine the intended cleaner error-handling approach for OData support and verify that existing OData behavior remains correct after the exception path is revised.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100