I12.6 · Watch Segment

Offen
#84 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
38/100
Issue-Typ
Feature
Klarheit
Klar beschrieben
Aktivitätsstatus
Aktiv
Tech-Stack
github, go, javascript, openapi, python

Rechercherichtung

Start by reading the parent issue, CONTRIBUTING.md, and the provider page template; then verify Segment’s official deprecation, changelog, API spec, and Python and JavaScript SDK sources, recording each source and the date checked. Identify a suitable plugin format for each source and add catalog entries, golden tests, and a replay fixture for a real historical breaking change. Add providers/segment.md and update docs/plugins.md; done means daily ingest emits events with source_url and exact source_excerpt, the replay produces the expected events, and the provider page lists each source with its check date.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

good first issue story

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

Story

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

Subtasks

  • Find Segment'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/segment.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 Segment 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
Vorherrschende Sprache
Go
Sterne
0
Forks
0
Ø Merge
2 Std. 59 Min.
Gemergte PRs (30 T.)
17

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus patch-it-dev/patch-it-plugins

Alle Issues in patch-it-dev/patch-it-plugins

Ähnliche Issues

Weitere Issues zu Go

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.