Is a component bound to just one element?

Question

I'm trying to wrap my head around Twitter flight. Lets say I have a Program page, it has 16 elements dealing with managing a program, CRUD operations, AJAX requests etc... Using twitter flight, do i need to create a component for each and every node element or for the Program page and attach each element to a function in the Program component?

score 3 · Accepted Answer · answered Apr 24 '13 at 21:07

3

A component is instantiated for each element you attach it to. If you have a list of DOM nodes, you can call .attachTo on each one and instantiate a set of components for all the nodes.

answered Apr 24 '13 at 21:07

imsky

3,239
17
16

score 1 · Answer 2 · answered Nov 25 '13 at 20:36

You don't have to attach a component to every node. You could have a single component attached to the document which does everything, but it makes sense to break that down in to smaller pieces of functionality. IMO, a component should represent a feature.

For example, you may have a component which communicates with an API via ajax, another which handles submissions for a particular form, another which manages the content of a list. Just how much a single component does is up to you. For the sake of portability, reusability and ease of maintenance it makes sense to keep components small and well-defined.

Saying that, you probably don't want to make lots and lots of tiny components. I wouldn't want to create one for every item in a list, but I might create one for every list on a page.

A single instance of a component can be attached to a DOM node. Components have access to the full DOM tree extending from their root node.

Is a component bound to just one element?

2 Answers2