Drop legacy entry point (only or stable4) #905
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
susnux
force-pushed
the
chore/drop-legacy-entry-point
branch
from
32351d8 to
e34c470
Compare
Only required on stable4 for Nextcloud 27.1 Signed-off-by: Ferdinand Thiessen <[email protected]>
susnux
force-pushed
the
chore/drop-legacy-entry-point
branch
from
e34c470 to
1487012
Compare
skjnldsv
approved these changes
Aug 17, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We should not go into that rabbit hole and maintain 3 different ways of spawning the file picker inside this library.
The legacy entry point is only required for Nextcloud 27.1 every other user should use the FilePickerBuilder as before.