OData lambda style filter query

[Tanddant]

Category

• Bug fix?
• New feature?
• New sample?
• Documentation update?

Related Issues

Based off the discussion over on #2781

What's in this Pull Request?

This PR is not completely done, but I needed a place to track the final changes (and docs) based off the input in #2781

• We like "method 1", seems simpler
• Drop "Field" from all the names so Lookup() vs LookupField().
• switch to camel case so Lookup becomes lookup()
• could simplify the names, equal instead of EqualsTo and notEqual vs NotEqualTo
  • I'm still open to the idea of having even shorter values, such as .eq(...) alongside the others, would like opinions
• Swap and/or for All/Some, just seems clearer to someone showing up with no knowledge of the filter methods
  • Not sure I'm the biggest fan, see Initial Pass at Lambda Filters - Seeking Feedback / Help #2781 for the reasons why
• pass in multiple objects you can use ...[] to gather them into an array within the method.
• this should be able to support all the filter cases, another reason to drop the "Field" name from the builder functions. Like for a site if you give it ISiteInfo you could filter on Text("Title").EqualsTo("blah");
  • The following is tested to work

  sp.web.lists.filter<IListInfo>(f => f.text("Title").equal("Employees"))

I'll happily start updating the docs once we have a "somewhat sign-off" on the above been done to an acceptable state 😊

[Tanddant]

Latest commit added "auto typing" for things like lists, webs, and so on, where we "know the type"

I.e

await sp.web.webinfos.filter(w => w.text("Title").equal('MyWebTitle'))();

Without having to specify that Title is a field on lists

I haven't tested this in every possible combination, but it looks to be working without breaking the list item stuff, should greatly improve the usability 😊