This library aims to:
- Improve Usability
- Reduce Boilerplate
- Reduce Rerendering
- Be Unobtrusively Designed
- Simple By Default, Complex If Desired
- Minimize & Encapsulate Dependencies
- Improve Logging / Traceability
DAOstack's Arc.js library defines an object model where each class instance represents a semantic object within the protocol (ex: DAO, Proposal, Member). These class instances interact with various contract in the protocol, and query their associative data model stored in the subgraph. Going forward, we will call these class instances "Entities".
Each Arc.react component creates an entity internally, and exposes the entity and its data to other components through React Contexts.
For Example: The component <DAO address="0x..."> contains an instance of class DAO. The class DAO instance can be accessed via the <DAO.Entity>, and its queried data can be handled via <DAO.Data>.
Note: There are also ComponentLists, which will be covered further down.
Each component has two important contexts:
- Data - The entity's data, queried from the subgraph.
- Entity - The entity's Arc.js class instance, useful for write operations.
In addition to these contexts, you can also access:
- Logs - The logs associated with this component.
Each part of the component is exposed through a React Context. This allows you to use different parts of the component throughout your application, while only defining it once farther up the DOM. See "Example 1" in examples.
For each component type, you can add an s after its name and it'll become a list of that entity type. For example: DAOs, Proposals, Members. See "Example 3" in examples.
Please see the examples document.