https://github.com/jamessimone/apex-collections

Turn that frown upside down by adding chainable collection filtering methods to Apex
https://github.com/jamessimone/apex-collections

apex collections salesforce salesforce-developers

Last synced: 3 months ago
JSON representation

Turn that frown upside down by adding chainable collection filtering methods to Apex

• Host: GitHub
• URL: https://github.com/jamessimone/apex-collections
• Owner: jamessimone
• Created: 2017-08-25T12:16:29.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2018-01-31T11:50:19.000Z (over 8 years ago)
• Last Synced: 2025-03-27T22:43:28.768Z (about 1 year ago)
• Topics: apex, collections, salesforce, salesforce-developers
• Language: Apex
• Size: 15.6 KB
• Stars: 18
• Watchers: 3
• Forks: 4
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

          
## Apex Collections - chaining support for filtering Apex collections.



  



Salesforce's Apex implementation of Java has no support for lambdas, which makes working with the equivalent of IEnumerable collections tiresome. Repeated "for(...) { method body }" loops abound

in Apex code.

Filter is a static helper class that can be chained to filter lists / other collections to:

1. Update existing SObject values with the help of a map with matching key value

2. Remove existing elements from a collection based on field level comparisons to a given value

3. Improve readability of code by drawing attention towards the intent of each iteration instead of the actual looping mechanic through collections.

### Example usage

    List filteredList = Filter.the(List myList)

        .byField(Schema.SObjectField myField)

        .to

        .filteredList()

    Filter.the(List myList)

        .whereField(Schema.SObjectField myField)

        .equals(Object valueOfMyFieldForAnyMatchingElement)

    Filter.the((Map) contactMap)

        .whereField(Schema.SObjectField myField)

        .is(null)

        .andReplaceFieldWithValueFrom(Schema.SObjectField fieldInBaseCollection, Map relatedMap, Schema.SObjectField fieldInRelatedMapToTakeValueFrom);

    Set filteredSet = Filter.the(List myList)

        .whereField(Schema.SObjectField myField)

        .isNot(null)

        .gather

        .also

        .whereField(Schema.SObjectField anotherField)

        .equals(Object valueThatWhereFieldShouldEqual)

        .gatherTo

        .filteredSet();

* first example returns List with any elements removed from the first collection. Depending on your use case, you may not care about the return value. If that's the case, you can drop the ".to.filteredList()" part.

* Maps require a cast to (Map) or (Map).  The second parameter in "andReplaceFieldWithValueFrom" is a map that needs to have a matching key value!  Useful if you are working with multiple maps at a time and need to update values in the first map with a field value from the second.

* Some functions / property calls are optional.  "also" , and "to" are merely there to assist in the readability.  If your list comprehensions level is over 9000, you may of course abstain from such things.