Andy in the Cloud

From BBC Basic to Force.com and beyond…

8 thoughts on “Change is inevitable so build for it!

  1. Absolutely incredible work / inspiration. TY so much for this – especially the LWC for syntax!

  2. Pingback: Change is inevitable so build for it! - Salesforce News & Tutorials

  3. Thank you for this post, I know many of us use this site as reference material. I was looking for material to reference while trying to write up an invocable class. I am not a developer and so I may be missing the context completely, but I was under the impression apex cannot be packaged in folder, yet the source material seems neatly packed into folders.
    Could provide some pointers on how that is achieved.

    • Thanks for the kind comments – inside the project folder you can place apex and some other files where you like tbh. The thing to keep in mind is the class names still need to be unique. So it’s really just a logical layout rather than physically how they show up in the org – which is still in one list. I personally like to use inner classes a lot to provide another layer. Then there is packages and namespaces which help further modularize between projects. Hope this helps – certainly a few options at least. Andy

Leave a Reply to Andrew Fawcett Cancel reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s