Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

API review and ongoing API quality controls

Aperta
#1,052 1 commento 0 reazioni 2 assegnatari Vedi su GitHub

@stephentoub ci sta già lavorando.

Dal 9/4/2026.

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

sdk-ga

Meta issue to represent some goals that @stephentoub and I discussed:

  1. Before GA, we need to do an exhaustive review of all our APIs, including all the codegenerated RPC ones
    • We might primarily pick one language as a representative - one that has good tooling for doing API reviews (so, C# then), and go through that end-to-end. For other languages we'd carefully review the most mainstream non-code-generated APIs but not re-do the review for codegenerated RPC.
    • The goal here is to identify names, shapes, and patterns that feel wrong or that we might not want to support in the long term
    • We know that a pretty large rpc.* API surface has appeared quickly and it hasn't been consistent about which things are flagged as experimental or not
  2. Before/beyond that, we want to be more organized about reviewing new RPC APIs that arrive with each runtime update
    • Proposal: the automation that updates @github/copilot and re-runs codegen should also output a cleanly readable list of all API additions/changes. We can ask it to flag breaking changes to non-experimental APIs too, but won't 100% rely on it detecting them. We will review the API changes as part of merging the PR that does a runtime update. This will entail extra effort for the first language we update for each runtime bump, but hopefully will be almost a no-op for subsequent languages.
  3. After the big naming change goes in, @stephentoub will look at extending the type metadata in the JSON schema to let us map to more idiomatic types in each language (example: timespans)
Lingua principale
Java
Stelle
10.5k
Fork
1.5k
Merge medio
1g 9h
PR unite (30g)
130

Guida per i contributori

Apri la guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di github/copilot-sdk

Tutte le issue di github/copilot-sdk

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.