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

docs(firestore-send-email): kit/extension parity – README differences and setup steps are wrong in several places

Abierto Apto para principiantes
  • ¿Algo no está bien?
#3,300 0 comentarios 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
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
72/100
Tipo de issue
Documentación
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
firebase, typescript
Área
documentation

Línea de trabajo

Empieza por las secciones del README de firestore-send-email enlazadas en el issue y su CHANGELOG; compara cada afirmación con el comportamiento reproducido de firebase-tools 15.31.0 que se indica en el issue. Actualiza las indicaciones sobre configuración, migración, región, parámetros y despliegue, incluidos los requisitos de paquetes y experimentos. El trabajo estará terminado cuando el README y el CHANGELOG describan con precisión todas las diferencias y soluciones alternativas indicadas.

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

Descripción

documentation kits parity

firestore-send-email kit/extension parity. Priority: low. Several README statements about setup and about the differences from the extension are wrong for firebase-tools 15.31.0.

Difference
README says Actually
Secrets are "named exactly SMTP_PASSWORD…", and the extension's secrets "are not picked up" (L157-L169) With a kit stanza they are kit-<instance>-<NAME>. ext:migrate reuses the extension's secret through FIREBASE_SECRET_REF_SMTP_PASSWORD (seen in a migrated .env)
The extension "offered no location setting" / "Nothing reads" FUNCTION_DEFAULT_REGION (L173-L175, L199-L202) Extensions have a location setting (an instance in europe-west2 was migrated). The install and migrate templates read FUNCTION_DEFAULT_REGION, and it decides the region when DATABASE_REGION is blank
Changing the region "deletes and recreates the function" (L216-L221) The CLI creates the new function before deleting the old one. A non-interactive deploy aborts with deletion cannot proceed in non-interactive mode unless you pass --force (reproduced)
EXT_SELECTED_EVENTS "cannot be set" (L227-L232) It is allowed, ext:migrate writes it, and the kit honours it (only onComplete was published when set)
A bad URI "fails at send time with delivery.state: ERROR" (L242-L243) A blank or unparseable URI leaves documents with no delivery field
Every variable "keeps its name, type and default"; "ported verbatim", "version 0.2.10" (L148-L153, L270-L272) OAUTH_PORT, OAUTH_SECURE and TTL_EXPIRE_VALUE changed type. Several optional params gained defaults. nodemailer is 7, not 9
The CLI "prompts for any required values that are missing" (L87-L88) A non-interactive deploy fails unless every param, including ones with defaults, is in .env
Configure "with a .env (or .env.<projectId>)" (L49) .env.<projectId>, which kits:install, ext:migrate and interactive deploys write, silently overrides edits to .env
Deploy example with instance id default (L57-L70) Fails in any project that already has a default functions codebase: "functions codebase name and kit instance ID must be mutually exclusive"
firebase ext:migrate is a supported path firebase-tools lists this extension as PENDING_PUBLISHER, so a plain ext:migrate fails with "does not have an associated function kit". It needs --package @firebase-function-kits/firestore-send-email@next and the extMigrationFeatures and secretEnvParams experiments
CHANGELOG: eventarcpublishing.googleapis.com "is enabled on your project whether or not you use events" A non-interactive deploy without --force fails with "Must enable required APIs to deploy" if the API is disabled
Reproduced

Each row was checked on the test project or against firebase-tools 15.31.0. The rows marked "reproduced" were run live.

Resolution

Correct each statement in the README and CHANGELOG. Document the --package / experiments requirement until the replacement listing is published.

Lenguaje dominante
TypeScript
Estrellas
979
Forks
436
Merge medio
2 d 13 h
PR fusionados (30 d)
18

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 firebase/extensions

Todos los issues de firebase/extensions

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.