I still get `missing multipart field` even after installing busboy for Cloud Functions about express-multipart-file-parser HOT 9 CLOSED

A bit of digging led me to this.. haven't tried it yet but I'm thinking of doing this instead. https://stackoverflow.com/questions/42775668/firebase-cloud-functions-multipart-form-data

from express-multipart-file-parser.

It seem it's an issue with the apollo server (I never used GraphQL before). Reading the docs (here) it seems there is no need to use any extra express middleware for file upload.
Also found this article that says you'll need to install the graphql-upload middleware.

As said at the stackoverflow question you linked, you could upload your file using the firebase web api and them send the path to your server. This is not ideal though

from express-multipart-file-parser.

Let me know if you get anywhere with this 😃

from express-multipart-file-parser.

I'll try that extra graphql-upload middleware you mentioned and let you know.

I stumbled across using createUploadLink here https://github.com/jaydenseric/apollo-upload-client although it isn't clear

Here is how I am setting up Apollo Client using the link attribute along with above server code:

import React from 'react'
import ReactDOM from 'react-dom'
import { ApolloProvider } from 'react-apollo'
import { ApolloClient } from 'apollo-client'
import { InMemoryCache } from 'apollo-cache-inmemory'
import { createUploadLink } from 'apollo-upload-client'
import { Provider } from 'react-redux'
import store, { history } from './Store'
import { ConnectedRouter } from 'react-router-redux'
import App from './App'
import registerServiceWorker from './lib/serviceWorker'
import './index.scss'
import { GRAPHQL_URL} from './constants/graphql'

const uploadLink = createUploadLink({
    uri: GRAPHQL_URL, // Apollo Server is served from port 4000
    headers: {
        "keep-alive": "true"
    }
})
const apolloCache = new InMemoryCache()

const client = new ApolloClient({
    cache: apolloCache,
    link: uploadLink,
    uri: GRAPHQL_URL,
});

ReactDOM.render(
    <ApolloProvider client={client}>
        <Provider store={store}>
            <ConnectedRouter history={history}>
                <App />
            </ConnectedRouter>
        </Provider>
    </ApolloProvider>,
    document.getElementById('root')
)
registerServiceWorker()

In your opinion, why is the stackoverflow question I linked "not ideal though"?

from express-multipart-file-parser.

from express-multipart-file-parser.

I agree with your assessment, initially my goal was to send a mutation over Firebase Cloud Function to GraphQL including some textual information along with a File (could be base64). The file would be uploaded to Firebase Storage and upon completion would be stored within Firebase Firestore (possibly using a Transaction to manage concurrency but I'm still debating this). Does this approach sound correct to you?

I also ran into this approach which shows that including uploads as a property on ApolloServer should be sufficient to use without the graphqlUploadExpress middleware, which I'm doing as you can see above.

PS: Do you suggest an alternative file storage? S3? Although this doesn't solve my issue with sending multipart/form-data over Cloud Functions to GraphQL because I'll still need to do that regardless of where store.

from express-multipart-file-parser.

from express-multipart-file-parser.

Closing as explained in the referenced issue (and possible solution)

from express-multipart-file-parser.

Did you ever solve this issue?

from express-multipart-file-parser.