New answers tagged design-patterns
1
vote
Accessing relationship fields in fflib
Selectors are just a mockable reusable wrapper around SOQL that can be independently unit tested.
A properly named selector like
ContactsSelector.newInstance().selectWithAccountByEmail(emails)
tells ...
1
vote
Accessing relationship fields in fflib
Yes, you can. First of all it is more about how your team prefer to handle such scenarios, but not about strict rules that everyone should follow. When I am choosing beetween different approaches I ...
1
vote
Accepted
About Design Pattern - Avoid excessive looping
tl;dr:
Don't worry so much about performance until you know it's an issue (and can measure it).
Just focus on making it easy to read and test, and keeping things like queries and DML outside of all ...
0
votes
About Design Pattern - Avoid excessive looping
A typical trigger framework (example) abstracts the trigger operation into three parts: bulkBefore(), action(record), and bulkAfter(). Note that this doesn't "save" any loops during ...
1
vote
Design patterns - benefits of using with Apex code
I have quite different views compared to the rest of the responses. Salesforce had a statement limit before the CPU limit came into the picture. Thus, it was extremely efficient to make things public ...
Top 50 recent answers are included
Related Tags
design-patterns × 139apex × 85
trigger × 26
bestpractice × 20
architecture × 8
visualforce × 7
unit-test × 6
design × 6
lightning-aura-components × 5
integration × 5
callout × 5
fflib × 5
soql × 4
api × 4
class × 4
data × 4
enterprise × 4
pattern × 4
domain-layer × 4
lightning-web-components × 3
visual-workflow × 3
interface × 3
oop × 3
lightning × 2
salesforcedx × 2