Fragment

[IzumiSy]

Fabrix can support fragment for directive configuration reusability.

The configuration given to fragments with fabrix directives are inherited into the query, so configurations can be reusable through fragments.

fragment IDNameParts on Todo @fabrix(input: [
  { field: "id", config: { hidden: true } }
]) {
  id
  name
}

query todos {
  allTodos {
    collection {
      ...IDNameParts
      status
   }
  }
}

If field configurations are duplicated between fragments and queries, those are merged into one with queries prioritized.

Fragment registration

Ideally, users can register their own component associated to a fragment.

Component registry is the place that supports those association.

componentRegistry.addFragment(
  query: gql`
    fragmment moKanbanView on ManufacturingOrder {
      collection {
        quantity
        status
        name
        description
      }
    }
  `,
  component: ({ values }) => {
    /*
     * {
     *   collection: {
     *     quantity: number
     *     name: string
     *   }
     * }
     */
    return (
      <Kanban 
        groupBy="status" 
        title="name" 
        body={(value) => (
          <KanbanDescription>
            {value.description}
          </KanbanDescription>
        )}
        values={values} 
      />
    )
  }
)

const Page = () => {
  return (
    <FabrixComponent
      contentClassName="grid gap-1"
      query={gql`
        query {
          manufacturingOrders {
            ...moKanbanView
          }
        }
      `}
    />
  ) 
}