Where GraphQL

Les applications doivent souvent alimenter un input GraphQL where depuis des filtres d’URL. Gardez ce mapping explicite: le schema filter-query possede la forme de l’URL, et un petit codec possede la conversion vers et depuis GraphQL.

import {
  booleanField,
  buildEqFilters,
  defineSchema,
  enumField,
  stringField,
  type InferFilters,
} from '@plumile/filter-query';

type ProjectWhere = {
  archived?: boolean;
  owner?: { id?: string };
  status?: 'ACTIVE' | 'PAUSED';
  title?: { contains?: string };
};

export const projectFilters = defineSchema({
  ownerId: stringField(['eq']),
  status: enumField(['ACTIVE', 'PAUSED'], ['eq']),
  title: stringField(['contains']),
  archived: booleanField(['eq']),
});

export type ProjectFilters = InferFilters<typeof projectFilters>;

export function toProjectWhere(filters: ProjectFilters): ProjectWhere | null {
  const where: ProjectWhere = {};

  if (filters.ownerId?.eq != null) {
    where.owner = { id: filters.ownerId.eq };
  }
  if (filters.status?.eq != null) {
    where.status = filters.status.eq;
  }
  if (filters.title?.contains != null) {
    where.title = { contains: filters.title.contains };
  }
  if (filters.archived?.eq != null) {
    where.archived = filters.archived.eq;
  }

  return Object.keys(where).length > 0 ? where : null;
}

export function fromProjectWhere(where: ProjectWhere | null): ProjectFilters {
  if (where == null) {
    return buildEqFilters({});
  }

  return {
    ...buildEqFilters<typeof projectFilters>({
      ownerId: where.owner?.id,
      status: where.status,
      archived: where.archived,
    }),
    ...(where.title?.contains != null
      ? { title: { contains: where.title.contains } }
      : {}),
  };
}

Utilisez des noms comme ownerId quand l’URL doit rester stable et lisible, meme si l’input GraphQL est imbrique. Gardez les alias et chemins imbriques dans cette couche de mapping plutot que dans l’UI.