Search icon
Subscription
0
Cart icon
Close icon
You have no products in your basket yet
Arrow left icon
All Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Newsletters
Free Learning
Arrow right icon
Apex Design Patterns

You're reading from  Apex Design Patterns

Product type Book
Published in Apr 2016
Publisher
ISBN-13 9781782173656
Pages 256 pages
Edition 1st Edition
Languages
Authors (2):
Anshul Verma Anshul Verma
Profile icon Anshul Verma
Jitendra Zaa Jitendra Zaa
Profile icon Jitendra Zaa
View More author details

The ignoring toString() method


Consider the following Apex class:

public class ToStringDemo {  
    public String companyName {get;set;} 
    public String city {get;set;}   
} 

A developer can print any important information about this class by running the following anonymous Apex code:

ToStringDemo obj = new ToStringDemo(); 
obj.companyName = 'Salesforce'; 
obj.city = 'SFO'; 
System.debug(obj); 

The output is as follows:

ToStringDemo:[city=SFO, companyName=Salesforce] 

In the preceding code, we are trying to print an object for debugging purposes. Internally, Apex calls the toString() method. As we have not overridden it, Salesforce uses its predefined className:[variable1=value,variable2=value,...] format to print the object value:

Ignoring the override of the toString() method is considered as an anti-pattern and we should implement it whenever possible.

Note

Every class in Apex is by default a child of the Object class. So, all the classes inherit...

lock icon The rest of the chapter is locked
arrow left Previous Chapter
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at ₹800/month. Cancel anytime}