CodeGenieApp / CodeGenieApp/serverless-express
Body data is not being parsed when programmatically invoking graphql handler in apollo-server-lambda v3
- Vorherrschende Sprache
- JavaScript
- Sterne
- 5.3k
- Forks
- 676
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
When programmatically invoking graphql handler in apollo-server-lambda v3, I receive the following error message: "POST body missing, invalid Content-Type, or JSON object has no keys.".
After reviewing the issue, I posted an [issue @ apollo-server](https://github.com/apollographql/apollo-server/issues/5504)
But it looks like the solution is to change the `@vendia/serverless-express` code as described below.
The body data is extracted by this code from utils.js (@vendia/serverless-express):
```javascript
function getEventBody ({
event,
body = event.body,
isBase64Encoded = event.isBase64Encoded
}) {
return Buffer.from(body, isBase64Encoded ? 'base64' : 'utf8')
}
function getRequestValuesFromEvent ({
...
if (event.body) {
body = getEventBody({ event })
const { isBase64Encoded } = event
headers['content-length'] = Buffer.byteLength(body, isBase64Encoded ? 'base64' : 'utf8')
}
...
}
```
But where is the code that `JSON.parse` the body data? Should it?
As an experiment, I changed the code from this...
```javascript
...
if (event.body) {
body = getEventBody({ event })
const { isBase64Encoded } = event
headers['content-length'] = Buffer.byteLength(body, isBase64Encoded ? 'base64' : 'utf8')
}
...
```
...to this:
```javascript
...
if (event.body) {
const decodedBody = getEventBody({ event })
const { isBase64Encoded } = event
headers['content-length'] = Buffer.byteLength(decodedBody, isBase64Encoded ? 'base64' : 'utf8')
body = JSON.parse(decodedBody);
}
...
```
and it worked as expected!
Should I submit a PR to @vendia/serverless-express ???
Beitragsleitfaden
Rechercherichtung
Beginne mit utils.js, insbesondere mit getEventBody und getRequestValuesFromEvent, und vergleiche die vom Apollo Server Lambda-Handler erwartete Body-Darstellung mit dem von serverless-express übergebenen Wert. Das Issue ist gelöst, wenn programmgesteuerte GraphQL-Aufrufe den Request-Body korrekt verarbeiten, ohne das bestehende base64- und content-length-Verhalten zu beeinträchtigen, und das relevante Verhalten verifiziert ist.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- aws, express, graphql, javascript, nodejs
- Bereich
- api, backend, cloud
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 25/100