I15.1 · Watch HubSpot

Abierto
#100 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
go, openapi

Línea de trabajo

Start by reading the parent issue and CONTRIBUTING.md, then use the provider template and the existing catalog and provider examples to identify the expected formats. Verify HubSpot’s official deprecation, changelog, OpenAPI, and SDK release sources, recording when each was checked; leave unknown details as TBD. Add source fixtures and expected events, including a historical breaking change, then check that the provider page, plugin catalog entry, and client fix note meet the acceptance criteria.

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

Descripción

good first issue story

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

Story

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

Subtasks

  • Find HubSpot'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/hubspot.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 HubSpot 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
Lenguaje dominante
Go
Estrellas
0
Forks
0
Merge medio
2 h 59 min
PR fusionados (30 d)
17

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 patch-it-dev/patch-it-plugins

Todos los issues de patch-it-dev/patch-it-plugins

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.