v3.1.2 - Bugfix for Set Filtering in Query.filterWhere() #48
jongpie
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Changes
Full Changelog: v3.1.1...v3.1.2
Metadata API Version Updated to v58.0
Bugfixes
Query.filterWhere()
when filtering onSet<T>
that would previously result in an exception due to invalid formatting in the generated query. Thanks to @ctcforce for reporting this (issue filterWhere() method doesn't process Set value parameters correctly #43) and thanks to @jamessimone for fixing it! (PR Fixes Set handling in filterWhere #44)Code Cleanup
Schema
&System
namespaces to explicitly include the namespaces (e.g.,SObjectField
is nowSchema.SObjectField
). This avoids installation issues due to naming collisions in orgs that have custom Apex classes with the same name as a class/enum in theSystem
namespaceInstallation Info
Core Unlocked Package - no namespace
sf package install --apex-compile package --wait 20 --security-type AdminsOnly --package 04t5Y000001TsbQQAS
sfdx package install --wait 20 --security-type AdminsOnly --package 04t5Y000001TsbQQAS
Core Unlocked Package -
Nebula
namespacesf package install --apex-compile package --wait 20 --security-type AdminsOnly --package 04t5Y000001TsbVQAS
sfdx package install --wait 20 --security-type AdminsOnly --package 04t5Y000001TsbVQAS
This discussion was created from the release Bugfix for Set Filtering in Query.filterWhere().
Beta Was this translation helpful? Give feedback.
All reactions