-
Notifications
You must be signed in to change notification settings - Fork 729
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial file upload concept #116
Conversation
@wpK: Thank you for submitting a pull request! Before we can merge it, you'll need to sign the Meteor Contributor Agreement here: https://contribute.meteor.com/ |
@wpK: Thanks a lot, happy to see this get in! I'll try to take a closer look tomorrow or else over the weekend. |
Hey, I'm sorry I haven't gotten to this yet. I'll be on vacation for the next week and a half, but I'll take a look after. |
@martijnwalraven No problem. Enjoy your vacation! |
@martijnwalraven I hope you have had a pleasant vacation. Is there any chance that the merge conflicts get resolved in the near future? |
@TheFellner I'm caught up in preparing for GraphQL Summit right now, but let's get back to this next week. I don't think this is ready to be merged, but it's a good starting point for discussing API design. |
Hey, Is it still something you are working on ? Thanks :) |
Please, someone, resolve this PR |
Is there anything we can do to help get this PR through? It'll be super useful to have it working in the client. |
Please merge this PR. Thanks. |
any news about this? is it released? |
This would be a great addition for us. Is there any news about it? Can we help somehow? |
Waiting for this. |
Would also support this pull request, file uploads are mainstreamed in apollo-server now |
I'm hoping to get this working on my fork here: It's still a work in progress today, but I hope to have it running very soon. I've resolved all the merge conflicts with master. |
Okay I've learned that there's a lot more to the schema codegen. Would need Apollo to figure this one out. My fork corrects for a conflict with Progress, but I couldn't actually get the implementation for the mutation hooked up. |
This is so needed.... seems like a major oversight to not support this. @otri I took at look at your PR, looks solid, but as you said, need support from the Apollo team for the codegen part it appears. |
Hi @wpK and @martijnwalraven Do you need any help here? |
I've learned that using graphql for file transport is not a good idea.
Turns out it's best to push your files using a regular REST API, and let
the meta data reflect the availability of the files. This keeps the
channel for graphql changes fast and light, and the REST API can be built
to be scalable for larger bulk transport in the future.
On Tue, Jun 11, 2019 at 22:31 Kim de Vos ***@***.***> wrote:
Hi @wpK <https://github.com/wpK> and @martijnwalraven
<https://github.com/martijnwalraven>
Do you need any help here?
I'm looking for this feature, so if you need help feel free to reach out!
🚀
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#116?email_source=notifications&email_token=AAHHYAVDJM4BPGJE753L3QDPZ6SKZA5CNFSM4DUWQMW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXND47A#issuecomment-500842108>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHHYAWHE757CVKII4HKXQ3PZ6SKZANCNFSM4DUWQMWQ>
.
--
…_______________________
Aaron Hilton
Steampunk Digital
mobile: +81 80 3947 6874 <+818039476874>
skype: otristudios
facetime: aaron@steampunk.digital
Monocle 3D Portrait <https://goo.gl/w0JV66>
|
@wpK Are you interested in continuing this PR? If not I can close it out for you and take a stab myself. |
Nope, go for it.
On Thu, Jul 11, 2019 at 04:27 Ellen Shapiro ***@***.***> wrote:
@wpK <https://github.com/wpK> Are you interested in continuing this PR?
If not I can close it out for you and take a stab myself.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#116?email_source=notifications&email_token=AAHHYAVMO5Y3FCNDH7EZGODP6YZ2PA5CNFSM4DUWQMW2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZUPQ2A#issuecomment-510195816>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAHHYAWGCPQM7YFQ6JPR46LP6YZ2PANCNFSM4DUWQMWQ>
.
--
…_______________________
Aaron Hilton
Steampunk Digital
mobile: +81 80 3947 6874 <+818039476874>
skype: otristudios
facetime: aaron@steampunk.digital
Monocle 3D Portrait <https://goo.gl/w0JV66>
|
@designatednerd I have a branch fork with the 0.10.1 working with file upload. I can rebase to 0.11.0 and open an PR? |
@kimdv absolutely! |
Closing this in favor of #626 since that one's been rebased |
@designatednerd I haven't touched this in awhile. Last time I checked the Apollo server was adding official file upload support and I never got around to updating to the new spec. I'll watch #626 and when I have some more time try to contribute where I can. |
File upload concept - Taken from #116
Co-authored-by: Zach FettersMoore <zach.fetters@apollographql.com> Co-authored-by: Maria Elisabeth Schreiber <maria.schreiber@apollographql.com> Co-authored-by: gh-action-runner <runner@Mac-1698338401160.local> Co-authored-by: Anthony Miller <anthonymdev@gmail.com> Co-authored-by: gh-action-runner <runner@Mac-1698344533451.local> Co-authored-by: Hesham Salman <iron-ham@github.com> Co-authored-by: Syed Zohair Abbas Hadi <45510142+zohairhadi@users.noreply.github.com> Co-authored-by: gh-action-runner <runner@Mac-1698701484703.local>
As discussed in #114, this is an example of file upload support without forcing to a specific server spec.
I made this PR to get the conversation going. The naming, progress handling, GraphQLFile input error handling all need to be improved on.
An example of use: