-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Posting file pointers to REST API #660
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
Comments
I think we could probably just remove the check for the URL. @nlutsenko thoughts? |
Files are required to have a This said, we could remove the limitation here, but I would actually recommend moving your file pointers to use a different system of pointers for files, or sticking a URL there might also be the case. |
How would their code have worked on Parse.com then? Would the pointer have just referenced the most recent file with that name? |
Actually, I take it back - we do enforce guarantee of files by name, so we might as well remove this restriction. And if we can't serve the file from a URL - then, yeah, that actually is absolutely fine, but to match it closer to api.parse.com - going to remove the restriction. |
Hey. We're transitioning onto
parse-server
. We had old code POSTing images to the REST API, immediately followed by POSTing data to another collection, with a pointer to that earlier image file.When we were fully on Parse, before using
parse-server
, we supplied data like this:where only a
name
and a__type
were necessary to define that relationship.Once we moved to
parse-server
, this code was breaking. It boiled down to this line which also looks for aurl
. We needed to change out the data we're POSTing to something like this:Maybe this information could be provided in migration docs, since we didn't see it there.
It might also be worth mentioning that we're now using the
S3Adapter
to store our newly-created files in a bucket.Thanks for everything! Overall, this migration is going far smoother than we could've expected.
cc @kyleseaman
The text was updated successfully, but these errors were encountered: