Fix status clearing with initial empty value
When selecting an emoji but not specifying a message, the internal
message value was null which caused a server validation error on
sending.
This fixes the SetStatusModal to always work with an empty string
upfront, as this is the value the field would have if edited and cleared
manually.
Signed-off-by:
Vincent Petry <vincent@nextcloud.com>
Showing
- apps/user_status/js/user-status-menu.js 0 additions, 0 deletionsapps/user_status/js/user-status-menu.js
- apps/user_status/js/user-status-menu.js.map 0 additions, 0 deletionsapps/user_status/js/user-status-menu.js.map
- apps/user_status/js/user-status-modal.js 0 additions, 0 deletionsapps/user_status/js/user-status-modal.js
- apps/user_status/js/user-status-modal.js.map 0 additions, 0 deletionsapps/user_status/js/user-status-modal.js.map
- apps/user_status/src/components/SetStatusModal.vue 2 additions, 2 deletionsapps/user_status/src/components/SetStatusModal.vue
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
File suppressed by a .gitattributes entry or the file's encoding is unsupported.
Please register or sign in to comment