Is having multiples properties chained togeather bad coding practice?

I've been designing some classes for my ASP.NET application and a couple of the classes have fields which are of other class types.  When I was coding my save methods, I found that I was chaining quite a few properties togeather simply to get a value, for example in order to access the value for a street address I would have to type Customer.Contact.Address.StreetAddress and that seems rather convoluted so I'm wondering if this is normal or did I design my classes badly which are below.

Thanks

 public abstract class Person
    {
        private string firstName;
        private string lastName;

        public Person(string firstName, string lastName)
        {
            this.firstName = firstName;
            this.lastName = lastName;
        }

        public string FirstName
        {
            get { return firstName; }
            set { firstName = value; }
        }

        public string LastName
        {
            get { return lastName; }
            set { lastName = value; }
        }
    }

Open in new window


The customer class is what is passed to the method that save to the the database.

public class Customer : Person
    {
        private string notes;
        private Contact contact;

        public Customer(string firstName, string lastName, Contact contact) :
            base (firstName, lastName)
        {
            this.contact = contact;
        }

        public Contact Contact
        {
            get { return contact; }
            set { contact = value; }
        }

        public string Notes
        {
            get { return notes; }
            set { notes = value; }
        }
    }

Open in new window


Contact class is used in Customer to store contact info

public class Contact
    {
        private Address address;
        private Company company;
        private List<ContactDetail> contactDetails;

        public Contact(Address address, Company company)
        {
            this.address = address;
            this.company = company;
            this.contactDetails = new List<ContactDetail>();
        }


        public Address Address
        {
            get { return address; }
            set { address = value; }
        }

        public Company Company
        {
            get { return company; }
            set { company = value; }
        }

        public List<ContactDetail> ContactDetails
        {
            get { return contactDetails; }
        }

        public void AddContactDetails(ContactDetail detail)
        {
            contactDetails.Add(detail);
        }

    }

Open in new window


Contact detail is a class that is decalred as a list in Contact to store multiple contact types

public class ContactDetail
    {
        private ContactType contactType;
        private string contactInfo;

        public ContactDetail(ContactType contactType, string contactInfo)
        {
            this.contactType = contactType;
            this.contactInfo = contactInfo;
        }

        public string ContactInfo
        {
            get { return contactInfo; }
            set { contactInfo = value; }
        }
        
        public ContactType ContactType
        {
            get { return contactType; }
            set { contactType = value; }
        }

    }

Open in new window


Address contains basic address info

 public class Address
    {
        public Address(string streetAddess, string cityName, string provinceName, string postalCode)
        {
            this.StreetAddress = streetAddess;
            this.CityName = cityName;
            this.ProvinceName = provinceName;
            this.PostalCode = postalCode;
        }

        public string StreetAddress { get; set; }
        public string CityName { get; set; }
        public string ProvinceName { get; set; }
        public string PostalCode { get; set; }
    }

Open in new window

obb-taurusAsked:
Who is Participating?
 
käµfm³d 👽Commented:
Exactly. Although, I think in that trivial example there wouldn't be much benefit. As your methods grow in size, and you are passing objects between multiple method calls within the same caller, then you would get a better benefit from what you are showing. For example:

public void RedactAddresses(Contact c)
{
    Address r = c.Addresses.ResidentialAddress;
    Address m = c.Addresses.MailingAddress;

    r.Street = RedactStreet(r.Street);
    r.City = RedactCity(r.City);
    r.State = RedactState(r.State);

    m.Street = RedactStreet(m.Street);
    m.City = RedactCity(m.City);
    m.State = RedactState(m.State);
}

Open in new window

0
 
p_davisCommented:
Be as granular as you can be... this will lend to easier maintenance and scalability. There are ways around lengthy property traversing.
0
 
obb-taurusAuthor Commented:
Can you give an example of what I might do to avoid the lengthy properties in this situation?
0
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

 
käµfm³d 👽Commented:
I personally prefer it--so long as the chain isn't too long--for readability, but that's not to say you cannot find ways to achieve the same level of readability by using local variables as well. I think "Customer.Contact.Address.StreetAddress" might be pushing it (length-wise) for my personal taste. I believe MS' recommendation is to use local variables rather than chaining. This can approach can be a bit easier to debug also.

One seemingly ironic thing, however, is that you often see method chaining used heavily in LINQ. It can be difficult, at times, to debug such chaining.
0
 
obb-taurusAuthor Commented:
Kaufmed, when you say to use local variables rather than chaining, do you simply mean something like the following?  

public Address GetAddress()
{
      Address address = Contact.Address;
      return address;
}

Open in new window


Or are you suggesting to create a local primitave variable such as a string and assign the value from Address to the string for example:

public string GetEmail()
{
      string address = Address.Email;
      return address;
}

Open in new window


Is this what you meant?

Thanks
0
 
obb-taurusAuthor Commented:
Just so I have an idea, what would the code for the method RedActStreet(r.street) look like in your example?  Sorry about asking for so much detail but for some reason designing classes from the ground up seems to be a challenge for me and when I ran into this situation it threw me for a loop.

Thanks
0
 
käµfm³d 👽Commented:
Mind you this is all hypothetical code, but perhaps something along the lines of:

public string RedactStreet(string street)
{
    string result = steet;

    if (street == "123 Main St.")
    {
        result = string.Empty;
    }

    return result;
}

Open in new window

0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.