I11.8 · Watch Appwrite

Ouverte
#76 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
35/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
Active
Stack technique
github, go, openapi
Domaine
api, backend

Piste de recherche

Start by verifying Appwrite’s official deprecation, changelog, OpenAPI, and Python and JS SDK release sources; record each source URL and the date checked in providers/appwrite.md. Read the plugin format guidance in CONTRIBUTING.md and the provider template, then choose a format for each source and add catalog entries. Add saved-source golden tests and a historical breaking-change replay fixture; done means daily ingest emits events with source_url and exact source_excerpt, and the provider page lists every source with its check date.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

good first issue story

Part of https://github.com/patch-it-dev/patch-it-plugins/issues/14

Story

As a developer whose code calls Appwrite, I want patch-it to know when Appwrite breaks, deprecates or retires something, so I get the fix before production does.

Subtasks

  • Find Appwrite's sources and record them with the date checked (verify, don't guess; leave TBD if unknown):
    • deprecations / sunset page
    • API changelog (RSS / Atom if there is one)
    • OpenAPI spec, if published
    • official SDKs and their release notes / changelogs (Python and JS first)
    • API versioning scheme (date-based, path, header, none)
  • Pick the format plugin for each source (OpenAPI, RSS, GitHub Releases, changelog file, registry, prose) and add catalog lines
  • Golden test: a saved copy of each source in, the expected events out
  • One real historical breaking change as a replay fixture
  • Provider page providers/appwrite.md from the template
  • Add or update its row in docs/plugins.md (see CONTRIBUTING.md)
  • Note what the client needs to fix it (existing handler, or a new fix kind in the client)

Acceptance criteria

  • Daily ingest emits Appwrite events, each with source_url and an exact source_excerpt
  • The replayed historical change produces the right events
  • The provider page lists every source with its date checked
Langage dominant
Go
Étoiles
0
Forks
0
Merge moyen
2 h 59 min
PR mergées (30 j)
17

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de patch-it-dev/patch-it-plugins

Toutes les issues de patch-it-dev/patch-it-plugins

Issues similaires

Plus d'issues Go

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.