Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

RFC: Use WordPress as your app's data store

Abierto
  • ¿Algo no está bien?
#2,679 1 comentario 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
graphql, json, typescript, wordpress
Área
backend, database

Línea de trabajo

This is an RFC describing a multi-stage data store; start by reading the linked storage and REST work in issue #2674. The RFC lays out follow-on work for collection registration, WPGraphQL support, and a JS client, but does not identify implementation files or tests. Before taking it on, check the project discussion for a decided scope; done would need to be defined for one specific stage.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

[Area] Core [Area] WordPress Plugin [Type] Feature

Idea

Faustabase (working name) is a faster way to give your app a database, using the WordPress site you already have. Turn on FaustWP's document store, save JSON from your app, and never silently lose a write.

flowchart TD
  App["Your app"] -->|REST or GraphQL| WP["FaustWP<br/>checks version"]
  WP --> T[("wp_faust_<br/>documents")]
  Admin["wp-admin<br/>Tools screen"] -.->|read-only| T

Why

  • You don't need a second database like Firebase or Supabase, or a custom plugin.
  • Normal WordPress and WPGraphQL saves let the last write win. Faustabase rejects a stale write with a 409.
  • Site owners can see the data in wp-admin, and WordPress users and roles control access.

Decided

  • Documents live in one dedicated table, grouped into collections like Firestore. History can be added later without migrating data.

  • REST and WPGraphQL can both get, update, delete, list and add documents, with the same version check.

  • Collections are admin-only until you register them. Registering a collection sets its access mode and a JSON Schema that WordPress validates, which is how a form or waitlist accepts public writes:

    register_faust_collection( 'waitlist', array(
	'access' => 'public-create', // or 'admin' (default) or 'owner'
	'schema' => array( 'type' => 'object', 'required' => array( 'email' ) ),
) );

  • A JS client for app servers would look roughly like this:

    const ref = store.collection('preferences').doc('user-42');
await ref.update((d) => ({ ...d, theme: 'dark' })); // retries on conflict

Plan

  1. Storage and REST: #2674.
  2. register_faust_collection with access modes and schemas.
  3. WPGraphQL support.
  4. The JS client.

Realtime, complex queries and high write volume are out of scope.

Lenguaje dominante
TypeScript
Estrellas
1.6k
Forks
157
Merge medio
1 d 5 h
PR fusionados (30 d)
121

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de wpengine/faustjs

Todos los issues de wpengine/faustjs

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.