Opinions are my own! Passionate about Software Engineering in the Salesforce space, and how to make the complex less daunting. "Go slow in order to go fast"
Introducing D2X, a new open source Salesforce DevOps tool designed to make it easy to launch projects fully configured to leverage all of GitHub that align with the Salesforce Well-Architected principles of Adaptable (Resilient and Composable). https://t.co/SSQVVGcsE9
January 23 Release Notes have been published for the DX@Scale Team. New Craft-First Frameworks available and as new features in sfpowerscripts to explore.
Head over and review whats new at https://t.co/fXfLHTKG5A
Thanks everybody for the support and collaboration!
Our lightweight trigger framework and associated sample bypass strategy are now open source. To help you decouple your components if you have embarked on your Salesforce modularisation journey.
https://t.co/mVojdEkJ8x and https://t.co/h9AfBL9YAq
@SalesforceDevs@dxatscale
It has been about 6 months since we adopted @dxatscale in @khealth. It is the best time and effort investment for our Salesforce delivery pipeline. To make it even more precise - I can't imagine working with other CI/CD solutions on this platform in the future.
#sfruslan
1/4 🧵
We all agree: Dev Teams need rules to be successful. But where is the sweet spot between anarchy and bureaucracy? My answer: Craftsmanship plus a few simple Ground Rules. I did a presentation about the rules I use at #SFSummit22 today. Here's the recording https://t.co/kGawr8pucC
@adamwathan, silly question: What is the "tailwindcss" way for the "font-stretch" property?
Seen Mona Sans and Hubot from @github, and they look gorgeous!
@AndrewDavis_io@dxatscale@ramziakremi The other benefit that I didn’t talk about is how that eases the data setup when you are testing the business logic.
@AndrewDavis_io@dxatscale@ramziakremi The beauty of testing in isolation. The Ruby or Elixir communities were our main source of inspiration. This requires to tuck away everything that triggers IO (database, network, ...)
2022 seems to be the year of Open Source Apex Parsers. Just 2 weeks ago #aheber published this one. It's JS-based and uses the Tree-Sitter parser generator.
https://t.co/8d3jjIVGq7
@rsoesemann@azlus So finally, I think that I am going to land on: the trigger handler responsibility is to re-create the business context, format and to rely on the Service to execute the business logic.
The handler is still a View :D
@rsoesemann@azlus The reason why we did that was that we didn't want the Service to handle the maps populated by the trigger.
The Service should be re-usable no matter what is triggering it (trigger, LWC, inbound integration)
@rsoesemann@azlus We had instances where we wanted to check the modification of a specific field and trigger the associated logic.
That "filtering" logic or better context creation was done in the handler.