-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Typo in new FileUpload options #7602
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
Thanks for opening this issue!
|
Nice catch! Would you be willing to submit a PR? |
Sure thing... Just need to know which one is correct 😁 |
If it’s consistently I think updating the documentation is the easiest approach. What do you think? |
Could you point to the documentation that is outdated? The https://github.com/parse-community/parse-server/blob/master/CHANGELOG.md |
I see that now in the changelog. This is my mistake, most of my projects specify the latest version but for some reason, this one had the full repo URL instead of a version so it grabbed master. I was thinking this was version 4.10.4 but you are correct, this project was on master by mistake. Might have been filled in "helpfully" by WebStorm or something. Well, we should probably leave this issue open for the time being because the bug still exists - just not in production. Given it hasn't been released yet, probably easiest just to update the Router to match the spec/doc/etc. I can send in this PR if that sounds like a plan. |
Could you point me to where in the project/documentation the " The merged spec seems to consistently use |
Yes you're right, I was looking at the outdated PR #6997 and grabbed the options from there. I thought it was weird that I couldn't find good documentation elsewhere, I guess it's been a long week... |
No worries at all! We'll add the full |
Makes sense. Thank you! |
This issue is for the latest release of Parse Server, 4.10.4, regarding #7071.
In all the documentation everywhere, and in the sample config, the new options are listed as:
I set these keys in my config but still couldn't get it to work. Finally after digging for a while, I realized in the actual FilesRouter.js where the config options are checked, it's listed as:
Note this shows
enableForPublic
instead ofenabledForPublic
as above.I don't know if this is a documentation bug or a bug in the Router, but I wanted to highlight this in case someone else was trying to get it working.
The text was updated successfully, but these errors were encountered: