fake set displayname support#151
Closed
butonic wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
I guess this needs to also meke it into the release branch |
Codecov Report
@@ Coverage Diff @@
## master #151 +/- ##
============================================
+ Coverage 25.56% 25.57% +<.01%
- Complexity 1311 1312 +1
============================================
Files 47 47
Lines 5022 5025 +3
============================================
+ Hits 1284 1285 +1
- Misses 3738 3740 +2
Continue to review full report at Codecov.
|
Contributor
Author
|
superseded by owncloud/core#29669, but still needs to go in to make it work with 10.0.4 |
Contributor
|
already in release branch - will be merged back in |
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
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.
core will only uppdate the account if the backend supports setting it. this is a workaround. needs fixing in core. but core should handle the sync update anyway.