Fixed last remains of GetAll vs GetMany
#17223
Merged
Conversation
This file contains 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
… inputted. Instead a GetAll overload have been introduced
5 tasks
nikolajlauridsen
deleted the
v15/hotfix/fix-last-remains-of-GetAll-vs-GetMany
branch
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.
Description
According to umbraco/Announcements#15 all services'
GetAllmethod has changed behavior, but a a few was not migrated yet.Changed the behavior to not return all items, renamed to
GetMany, when no keys received. Instead a newGetAllmethod is introduced that do not take any parameters.