Jas Valgotar

WIP: Adds warning on comparing same FirstNameNode

3

This pull request introduces a warning when comparing two identical FirstNameNode instances, which could be either global or scoped variables. This enhancement is particularly beneficial in scenarios involving scoped variables,...

Improves error message when putting value inside record and table.

11

Fixes https://github.com/microsoft/Power-Fx/issues/2196

For Expression where the user by mistake assigns the void type to the record field, e.g. `{out : Remove()}` we give the below error. `Incompatible type. The item you are...

`First(ShowColumns(Accounts, 'Account Name')).'Account Name'` should work. but it only allows logical names, Ie forces to use `First(ShowColumns(Accounts, 'Account Name')).name` Add back the below test, re-weritten with ShowColumns() to **DisplayNameTests.cs>ValidateDisplayNames** `[InlineData("First(Nested.Inner).Inner",...

ShowColumns(), DropColumn(), Search(), etc... should suggest columns Arg. e.g. `ShowColumns(Accounts, |)` should suggest all the columns of Accounts. And same for DropColumn()

Connectors namespace should be able to use Display name in an expression.

3

Currently if you use connectors via Dataverse Plugins, it only uses Logical Name in expression, it should also allow display name.

We don't support Remove() overload in C# interpreter, we should implement this for better parity across Power Fx hosts. `Remove( DataSource, Table [, RemoveFlags.All ] )`

We should not be adding TexlFunctions in C# interpreter engine which are not supported at runtime. Rather we should investigate the feasibility of showing this at error Authoring time. e.g....