Structuring our data with classes

Let's define a simple class to represent a person. Right now we only have one person represented in the project—the owner—but in the future we may have more people, such as employees. It will be helpful to have a class that encapsulates all the shared logic for dealing with people. We'll start out with a simple class:

class window.Person
  constructor: (@name) ->

Right now our class contains only a constructor. We learned in the previous chapter that putting @name in the constructor arguments automatically assigns it as a property of the new object.

We'll put this class in a new file, named person.coffee. Having each class in a separate file is a good convention to follow. Since classes naturally encapsulate shared ...

Get CoffeeScript Application Development now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.