2.2.4.7 release notes
2.2.4.7
- Issue 2240 - When scratch org creation fails, the user is now prompted to reopen the scratch org creation dialog with the exact same settings so that the reported issue(s) can be corrected and the creation retried.
- Issue 2244 - Fixed an issue with the resolution of inherited inner types more than a single level of inheritance "away" from the point of usage.
- Issue 2246 - Fixed a few SOQL issues:
- The argument for
GROUPING
should now be handled properly as a qualified field name. - Specialized completion insert handlers should now behave properly in standalone SOQL queries, i.e., those in the SOQL Query tool window and in
.soql
files. WITH SECURITY_ENFORCED
andALL ROWS
clauses are now flagged as invalid in standalone SOQL queries as they're only allowed in Apex query expressions.
- The argument for
- Issue 2247 - Fixed a regression from the recent constructor improvements where an implicit constructor, either the default no-arg constructor or a default
Exception
constructor, would be included in a rename operation for the containing top-level class causing it to fail. - Fixed a few specific
.forceignore
patterns that weren't resolving properly. - I wasn't very happy with the default reference tracking behavior in
.forceignore
files so I've added a custom reference contributor that should hopefully do a much better job of adding references to all files affected by each entry path component even when wildcards are used. - Fixed an issue where declarations of interface types weren't being treated polymorphically as type
Object
, specifically lacking the inheritedtoString()
,equals()
, andhashCode()
methods. - External lookup fields in custom metadata types should have type
String
instead of typeId
. This change requires OST regeneration, though if you've not experienced any issues from it there's no need to regenerate just for this. - Fixed a reference resolution issue with compile-time field constants of the form
TypeName.FieldName
used asupsert
external IDs. - Fixed a reference resolution issue with compile-time field constants of the form
Schema.TypeName.fields.FieldName
. - Other minor fixes and improvements.