Uh oh!
There was an error while loading. Please reload this page.
Conversation
artonge
left a comment
There was a problem hiding this comment.
Hello @R0Wi,
Could you set a proper name to the issue and commit ?
The issue is that the values are saved in a generic string column in the DB. So they are returned as string by the API, as is it not possible to know in which type to cast them.
Your solution seem fine to me :)
Fix for #35645 Signed-off-by: GitHub <noreply@github.com>
R0Wi
commented
Feb 27, 2023
Done ✔️
Yes already spotted this but I wondered why the problem came with NC 25 since I think there hasn't been changed much in this area? Maybe an update of the NC Vue components is responsible for this. |
artonge
commented
Feb 27, 2023
Thanks :) Not sure. Worth noting that we recently moved to a new select component: #36754 so it might be useful to check if the bug still occurs with it. |
R0Wi
commented
Feb 27, 2023
According to https://github.com/nextcloud/nextcloud-vue/blob/1ed5694799d108cc03e287c2215b14e56d7c4df5/src/components/NcSelectTags/NcSelectTags.vue#L241 and the logic there, the component still expects the passed |
R0Wi
commented
Feb 28, 2023
/backport stable25 |
R0Wi
commented
Feb 28, 2023
@szaimen any chance to get this backported to NC 25? |
szaimen
commented
Feb 28, 2023
/backport to stable25 |
Summary
Did some research to help fixing R0Wi-DEV/workflow_ocr#179 and found out, that the NC Vue component for system tags expect numeric ids as values (either a single tag id or an array of tag ids which are selected). The server API for workflows deliveres the system tag ids as strings:
The temporary fix is to convert them on clientside into integers.
TODO
Checklist