I11.8 · Watch Appwrite

Aberta
#76 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, go, openapi
Domínio
api, backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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
Linguagem predominante
Go
Estrelas
0
Forks
0
Merge médio
2h 59min
PRs com merge (30d)
17

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de patch-it-dev/patch-it-plugins

Todas as issues de patch-it-dev/patch-it-plugins

Issues semelhantes

Mais issues de Go

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.