Behind the scenes
If you're paying attention to the Package Explorer view in the Force.com IDE, you might have noticed that after creating our class, instead of one new file being created, there were two. The same thing happened after we created our trigger too, as shown in the following screenshot, which shows metadata files exist for each class and trigger:
You're not seeing double; these extra files are intentional and serve an important purpose. Remember back in Chapter 2, Apex Limits, when we looked at the metadata for our Apex code. These extra files store that metadata. In Apex classes, you can control the API version under which the code ...
Get Learning Apex Programming now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
