refactor(database): columns -> cells

[doodlewind]

Lacking the concept of cell leads to serious ambiguity and incorrect variable naming in current database implementation. So the decision is to rename the ext:columns nested map to ext:cells, which is indeed a two-dimensional map (rowId + columnId) that contains database cells.

Before (nuanced "column" concept):

  getColumn(model: BaseBlockModel, schema: ColumnSchema): BlockColumn | null {
    const yColumns = this.yColumns.get(model.id);
    const yColumnMap = (yColumns?.get(schema.id) as Y.Map<unknown>) ?? null;
    if (!yColumnMap) return null;

    return {
      columnId: yColumnMap.get('columnId') as string,
      value: yColumnMap.get('value') as unknown,
    };
  }

After (yCells -> yRow -> yCell):

  getCell(model: BaseBlockModel, schema: ColumnSchema): Cell | null {
    const yRow = this.yCells.get(model.id);
    const yCell = (yRow?.get(schema.id) as Y.Map<unknown>) ?? null;
    if (!yCell) return null;

    return {
      columnId: yCell.get('columnId') as string,
      value: yCell.get('value') as unknown,
    };
  }

For future kanban view, we can still group them based on different values on the same column (columnSchema).

After this is landed, I would continue renaming columnSchema to column, which reflects the table structure better.

[codesandbox]

  Open in CodeSandbox Web Editor | VS Code | VS Code Insiders

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
blocksuite	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 3, 2023 8:37am
blocksuite-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 3, 2023 8:37am
blocksuite-react	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Apr 3, 2023 8:37am