-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Conversation
@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. |
Please fix it in one way only, either the upstream way or our way: |
didn't you add a check in the register method to check for |
I fixed it in the one hacky way to align with upstream ;) |
👍 fine by me
Will rebase |
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.
Signed-off-by: Morris Jobke <[email protected]>
e07f723
to
b373f52
Compare
@LukasReschke @nickvergessen @rullzer Should we backport this to stable10? @enoch85 requested it |
fine by me |
I tested this and it works 👍
cc @rullzer @icewind1991 @nickvergessen