Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This pull request introduces significant updates to the
RecordCollection
class in thesrc/apex/utils/classes/RecordCollection.cls
file. The main changes involve improving type safety and adding new functionality to handle records based on specific fields.Key changes include:
Type Safety Improvements:
sObjectType
member and added validation to ensure that therecords
list has a definedsObjectType
in theRecordCollection
constructor. Introduced a newTypeException
class to handle type-related errors.add
methods to include type checks, ensuring that only records or collections of the samesObjectType
can be added to theRecordCollection
.New Functionality:
segmentOnField
method that segments the records in theRecordCollection
based on a specified field, returning a map of field values to lists of records.These changes enhance the robustness and flexibility of the
RecordCollection
class, making it easier to manage and manipulate collections of SObjects while ensuring type consistency.