I'm also with file uploads. Examples in yoga look ...
# orm-helpt
terion
05/22/2018, 6:11 PMI'm also with file uploads. Examples in yoga look great, but IRL there are some not very good things in part of inputs. Is there a better way, than like this?
https://www.prisma.io/forum/t/proper-datamodel-for-file-uploads/3569
m
medelman
05/22/2018, 6:15 PMI think a lot of it will come down to how you want to store the files. Did you have a methodology in mind?
t
terion
05/22/2018, 6:16 PMUpload them to S3
terion
05/22/2018, 6:18 PMHow to handle incoming files that's a separate topic. The problem is with schemas, because Yoga server requires file fields inputs to be typed
Uploadm
medelman
05/22/2018, 6:21 PMYou don't have to use the built in types. I just create my own, like:
Copy code
type Media {
id: ID! @unique
createdAt: DateTime!
updatedAt: DateTime!
filename: String!
localSource: String!
uploadUri: String
bucket: String
key: String
region: String
owner: User
}t
terion
05/22/2018, 6:22 PMHm. And how do you handle multipart file requests?
m
medelman
05/22/2018, 6:24 PMI let S3 handle that using signed URLs
medelman
05/22/2018, 6:24 PMSo basically the user lets me know that he or she has a file to upload. I generate a signed URL on the server side as part of the mutation and return that data to the user.
medelman
05/22/2018, 6:24 PMThe user then says, 'Ok, I see that URL' and makes a post request.
medelman
05/22/2018, 6:25 PMFile never touches my GraphQL server
t
terion
05/22/2018, 6:25 PMAh. That's kinda nasty hack ))
m
medelman
05/22/2018, 6:26 PMI'm not sure I would consider it a hack. 🙂
t
terion
05/22/2018, 6:29 PMWell.. in any case I've got the idea, thank you, but it is better to utilize multipart graphql I think
m
medelman
05/22/2018, 6:30 PMAs long as your server has enough RAM to mitigate the potential memory bottleneck at scale.
2 Views