-
Notifications
You must be signed in to change notification settings - Fork 816
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
Make QML code more declarative by using properties #2221
Conversation
/rebase |
217c1c9
to
92ceef8
Compare
Needs some care for when no accounts are availabe |
Ping? |
92ceef8
to
0696f9a
Compare
/rebase |
0696f9a
to
fdcddfd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Very nice work, just a bunch of nitpicks left really.
fdcddfd
to
a473a55
Compare
/rebase |
By using properties and property bindings the QML code gets more declarative rather than imperative, which is considered better. This patch: - Introduces a currentUserId property in UserModel that replaces the equivalent Q_INVOKABLE call - Introduces an avatar property in User that contains the avatar's image provider url without any fallback - Introduces new image provider urls for fallback images - Moves the fallback image selection to QML since we want different fallbacks according to where it is used - Wires up the necessary signals to propagate a changing avatar Signed-off-by: Nicolas Fella <[email protected]>
a473a55
to
f586092
Compare
AppImage file: Nextcloud-PR-2221-f5860928d9179d31e4226794ecb47af6440b1319-x86_64.AppImage |
By using properties and property bindings the QML code gets more declarative rather than imperative, which is considered better.
This patch:
Signed-off-by: Nicolas Fella [email protected]