Avoiding escaping references with custom objects, part 1

- [Instructor] So, that's okay for collections,…but what should we do about other types of objects?…Let's suppose that we want to add a method…into our customer records that allows us…to retrieve a single object from the collection,…so we'll do that down here.…We'll call it getCustomerByName,…and it'll return a customer object,…(typing)…and so we'll pass in a string,…which is the customer's name that we're looking for.…

Now, when we created the map, the keys…are actually set to be the customers' names.…So, all I need to do to implement this method…is to return (typing) this.records.get,…and the value that is associated with…the key of the customer's name.…So, once again, what we've created here is some risky code.…We've provided an escaping reference to the customer object.…A client that calls getCustomerByName…is going to get a reference to the customer,…and can now call any of the methods…on this customer object that change its values.…

For example, in customer there's a set name method,…and it could call that and change the customer's name.…