Separation of concerns
pmmenzel opened this issue · comments
Based on feedback:
- Should separate out the "materialized" models from SF into their own models or modules. Calls to the salesforce api everytime you need to check something is inefficient and expensive.
- Need to cache information pulled from database to reuse again.
- Need to handle edge cases
- when you look up an email and nothing comes back.
- Mentioned using model to handle this because when a model comes back nil it doesn't blow up in at you.
- when you look up an email and nothing comes back.