Potential Pitfalls

1. Avoiding naming a Symbol’s Class the same as it’s Base Class unless no other Symbol will ever extend that Base Class. If a Symbol has the same Class name as its Base Class, its Timeline definitions will be merged with the Base Class which may cause problems for other subclasses of said Base Class.

If no other subclass of the class will exist, we recommend using the Base Class as the Class, and providing no Base Class for the symbol. This will tightly couple the Base Class and the Symbol such that when you instantiate a new instance of that Base Class, the Symbol will automatically be tied to it without using a lookup like getDefinitionByName().