Skip to content
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

Hack to prevent warning for read-only wrapper in public links #2122

Merged
merged 2 commits into from
Nov 16, 2016

Conversation

@MorrisJobke MorrisJobke added 3. to review Waiting for reviews downstream labels Nov 14, 2016
@MorrisJobke MorrisJobke added this to the Nextcloud 11.0 milestone Nov 14, 2016
@mention-bot
Copy link

@MorrisJobke, thanks for your PR! By analyzing the history of the files in this pull request, we identified @schiessle, @rullzer and @icewind1991 to be potential reviewers.

@nickvergessen
Copy link
Member

Please fix it in one way only, either the upstream way or our way:
#1722

@rullzer
Copy link
Member

rullzer commented Nov 14, 2016

didn't you add a check in the register method to check for read-only? That can go now then right?

@MorrisJobke
Copy link
Member Author

Please fix it in one way only, either the upstream way or our way:
#1722

I fixed it in the one hacky way to align with upstream ;)

@nickvergessen
Copy link
Member

👍 fine by me

Conflicting files
lib/private/Files/Filesystem.php

Will rebase

Vincent Petry and others added 2 commits November 16, 2016 19:04
Storage wrappers should normally always be registered inside a presetup
hook. However in the public link scenario this is not possible and
there is currently no good alternative with the current architecture.

Instead of logging a warning every time, this fix prevents the warning
to be shown but also adds a FIXME in the code for the future. This is
ok because this app is already using private/internal APIs at the
moment and should be reworked properly in the future.
@MorrisJobke MorrisJobke merged commit 8a02647 into master Nov 16, 2016
@MorrisJobke MorrisJobke deleted the downstream-26520 branch November 16, 2016 23:54
@MorrisJobke
Copy link
Member Author

@LukasReschke @nickvergessen @rullzer Should we backport this to stable10? @enoch85 requested it

@nickvergessen
Copy link
Member

fine by me

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Storage wrapper warnings
4 participants