Adithya Selvaprithiviraj

IntelliSense fix for UDFs

2

We need partial parse invalid UDF definitions for Intellisense to suggest options, This PR adds logic to return parse invalid UDF IRs which can be used by Intellisense .

Handle recursive types in UDFs

1

As we plan to support complex types from Datasource in UDFs, we want to handle recursively defined types in UDFs.

https://github.com/microsoft/Power-Fx/pull/2569#issuecomment-2289843518 As mentioned in the comment above , it imperative UDF parsing could be broken and it needs to be fixed

Enable UDF on REPL

6

Adds ability to define User-defined functions in REPL. Parsing UDFs requires a different parser from the Texl Expression parser and this is addressed by using the DefinitionsParser as a fallback...

Create a new IR Node to represent TypeLiterals and NamedTypes

1

Today we serialize the TypeLiterals and NamedTypes to strings and then deserialize it into DType in the runtime implementation of a function. Having a separate IR node for this would...

{Draft] Rename UntypedObject to Dynamic at user level

1

Renames UntypedObject to Dynamic at end user perspective. Internal name UntypedObject stays the same

Fix Aggregate types in UDF

2

Changes behavior of aggregate types like records and tables in User Defined Functions (UDFs) Add stricter type checking (restrict allowing more fields than expected) for aggregate types in UDF argument...

[DRAFT] UDT in REPL

2

draft to play around with UDT in REPL 

Methods in TexlParser take parser options which has PfxV1 and also features , there is a scope for cleanup and using just one there. Format and FormatUserdefinitions APIs can also...