We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It feels like these could be moved out to a child repository e.g. _contentRepostory.Users().Current().XYZ:
_contentRepostory.Users().Current().XYZ
The text was updated successfully, but these errors were encountered:
Fixes #473 IAdvancedContentRepositoryUserRepository: Move "Current" o…
48fbc9a
…ut to own child repository
Fixed, will be released in v0.10. The API has a breaking change, with methods moved under the new "Current()" extension method e.g.
var user = await _contentRepository .Users() .GetCurrent() .AsMicroSummary() .ExecuteAsync();
is now:
var user = await _contentRepository .Users() .Current() .Get() .AsMicroSummary() .ExecuteAsync();
Sorry, something went wrong.
No branches or pull requests
It feels like these could be moved out to a child repository e.g.
_contentRepostory.Users().Current().XYZ
:The text was updated successfully, but these errors were encountered: