Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Transfer ExpressionEngine from another repo #50

Open
thygesteffensen opened this issue Dec 14, 2022 · 1 comment
Open

Transfer ExpressionEngine from another repo #50

thygesteffensen opened this issue Dec 14, 2022 · 1 comment
Assignees

Comments

@thygesteffensen
Copy link
Owner

The ExpressionEngine have been extracted from this project and used as a standalone package on other projects, still following the Power Automate Expression format.

The tandalone project have had many updates and is more usable and stable, I will upload the repo later and start the transition.

@thygesteffensen
Copy link
Owner Author

Microsoft have open sourced the code for PowerFx, where Power Automate expression is a subset of PowerFxs capabilities.

From a glance, PowerFx implements the same functions (add, sub etc), but using Pascal case instead of camel case.

PowerFx can do more than what is allowed in Power Automate.

  • Look into replacing expression engine with PowerFx
  • Look into adding an intermediary, to keep the same API as expression engine.
  • Is some kind of expression analysis needed, can this be done with a seperate parser.
  • How does outputs and variables get handled
  • What about the license

It would be nice to switch to focus on executing flows locally, and if Microsoft should make a change and use PowerFx in flows, PAMU is ready 💪

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant