Let Us Use C# in Data Mapper v2 - We Promise Not to Abuse it #1358
erwinkramer
started this conversation in
Feature Ideas/Requests
Replies: 1 comment
-
Yes an inline C# scriptoid would be nice. Also support for extension dll's would be nice |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hey team, loving the slick new UX in Data Mapper v2—really, kudos! It's come a long way. But I do have one teeny-tiny, not-at-all-important feature request: can we please use custom C# functions?
I mean, sure, dragging lines around and stitching together a Franken-expression of nested built-ins is a fun retro puzzle, but sometimes you just want to write a quick MyCustomTransform(string input) and move on with life.
Yes, we get it—standardization, portability, etc. But for those of us living in the real world of legacy formats, quirky APIs, and business logic that no built-in function was ever meant to handle—custom C# functions are not a luxury. They're survival.
So how about it? Give us a little sandbox. We'll behave (probably).
And just to be crystal clear: we're not asking for custom XSLT functions. We're asking for C#. You know, the modern, maintainable, actually-pleasant-to-write language that we already use across the rest of our Logic Apps and Azure Functions. Let’s be honest—XSLT had its moment in the sun (circa 2005), but we’ve all moved on. Let it rest.
Thanks in advance,
A developer slowly losing the will to nest another substring(indexOf(...))
Beta Was this translation helpful? Give feedback.
All reactions