microsoft / microsoft/Power-Fx
ApplyGetLogging shouldn't enumerate all fields
Open
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 3.4k
- Forks
- 358
- Avg merge
- 10h 34m
- Merged PRs (30d)
- 3
Description
Enumerating fields is potentially very expensive - especially for CDP types where there could be relationships involved.
CheckResult.ApplyGetLogging() out to be cheap. But it apears to be triggering an enumeration.
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 CheckResult.ApplyGetLogging() and tracing the field enumeration it triggers, especially for CDP types with relationships. The issue is done when applying get logging avoids enumerating all fields and remains cheap; no specific file or test is named, so identify the relevant coverage while investigating.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100