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

v4.7.0 Release merge to main #3168

Merged
merged 38 commits into from
Nov 18, 2024
Merged

v4.7.0 Release merge to main #3168

merged 38 commits into from
Nov 18, 2024

Conversation

patrick-rodgers
Copy link
Member

Merge to main for 4.7.0 release

bcdmi and others added 30 commits August 19, 2023 08:09
This solved the issue where if you reused the same variable name in your long queries it broke
down to one warning which I can't resolve
# Conflicts:
#	package-lock.json
#	packages/sp/spqueryable.ts
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
Swap and/or for All/Some, just seems clearer to someone showing up with no knowledge of the filter methods
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");
…ng-exports

added missing exports to graph/presets/all
@patrick-rodgers patrick-rodgers merged commit 7252895 into main Nov 18, 2024
1 check failed
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

Successfully merging this pull request may close these issues.

6 participants