microsoft / microsoft/Power-Fx

Implement missing functions in Interpreter

Open
#284 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

good first issue
Dominant language
C#
Stars
3.4k
Forks
358
Avg merge
10h 34m
Merged PRs (30d)
3

Description

The interpreter doesn't implement all Power Apps functions yet.

See list of power apps functions: https://docs.microsoft.com/en-us/power-apps/maker/canvas-apps/formula-reference

List of functions implemented in Interpreter is at: https://github.com/microsoft/Power-Fx/blob/main/src/libraries/Microsoft.PowerFx.Interpreter/Functions/Library.cs

Looking at history for that file is an easy way to spot when new functions were added.

Here's are some good previous examples:

Function PR
Lookup() https://github.com/microsoft/Power-Fx/pull/212
Index() https://github.com/microsoft/Power-Fx/commit/2b16f6faf9ceaf22e7ca268b3c82d60ea2077ef6
Find() https://github.com/microsoft/Power-Fx/commit/b175c1fea3c276fbcb8f32270def09e531e42f4b
Boolean() https://github.com/microsoft/Power-Fx/commit/27bd908ec78408704cb2634dd34ebf1919da1e17

Writing test cases
For each function, there should be an individual .txt test case file.
Check expected behavior against Power Apps -with error handling enabled.
image

Good test cases for the functions include:

  • success cases
  • failure cases (like passing out-of-range values)
  • Passing Blank() or Error values

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the Power Apps formula reference and src/libraries/Microsoft.PowerFx.Interpreter/Functions/Library.cs, using its history and the linked examples to select a missing function. Add an individual .txt test case file for the function, covering success, failure, Blank(), and Error values with expected Power Apps behavior. Done means the function is implemented and its tests pass.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
compilers, testing-qa
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.