Allow viewing the raw request and response for debugging when using the SDK
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 25/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- node.js, typescript
- Área
- api
Línea de trabajo
The issue names no files or tests. Start by tracing the Graph client and call middleware request pipeline; determine how a debug mode or middleware callback could expose request and response URLs, payloads, and headers. Done means callers can inspect this information in Node applications without using a proxy.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Feature Request
Is your feature request related to a problem? Please describe
When using the SDK, sometimes I want to debug the call. Often this happens when a call fails and I want to verify what's going over the wire and what's coming back to determine if it's the Graph API or the SDK that's failing.
Describe the solution you'd like
I'd like to be able to put the Graph client, or a call in debug mode, where I get to see the request and response (URL + payload + headers) that go over the wire.
Describe alternatives you've considered
In a browser I can get this information from the network tab, but in Node apps, this would require a proxy which is inconvenient.
Additional context
Perhaps we could use implementing this feature using middleware, where we offer additional middleware that's logging requests and responses to console or better yet, offers a callback that allows me to decide how I want to deal with the information.
- Lenguaje dominante
- TypeScript
- Estrellas
- 833
- Forks
- 240
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de microsoftgraph/msgraph-sdk-javascript
-
status:waiting-for-triage
Dificultad 1/5 Menos de una hora Aptitud para principiantes 62/100
-
Is anyone here? Abierto
Dificultad 4/5 3-5 días Aptitud para principiantes 25/100
microsoftgraph/msgraph-sdk-javascript#2005 · 1 reacción ·
-
Is it really correct that the Javascript version of the graph SDK doesn't offer typed requests? Abiertostatus:waiting-for-triage
Dificultad 5/5 Más de una semana Aptitud para principiantes 42/100
-
status:waiting-for-triage type:bug
Dificultad 3/5 1-2 días Aptitud para principiantes 48/100
microsoftgraph/msgraph-sdk-javascript#1999 · 2 comentarios · 1 reacción ·
-
status:waiting-for-triage type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 45/100
Todos los issues de microsoftgraph/msgraph-sdk-javascript
Issues similares
-
[Bug]: Discord Activity titles with emoji are rejected as over 80 characters when they are not Abiertoclawsweeper:linked-pr-open clawsweeper:no-new-fix-pr clawsweeper:source-repro impact:message-loss issue-rating: 🦞 diamond lobster maturity:stable P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
Eynzof/Hermes-CN-Desktop#616 ·
-
ZCode 3.14.3 に対応する Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
supermomonga/zcode-acp#24 ·
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
growthbook/growthbook#7100 ·
-
triage
Dificultad 1/5 1-3 horas Aptitud para principiantes 88/100