docs(API): Clarify the user field on translation schema#953
docs(API): Clarify the user field on translation schema#953
Conversation
|
I guess we can wait on this PR? Until we have a final decision on how to proceed about this problem? Maybe we decide to add a new attribute? |
|
@hahmed-dev I think it's not very realistic to add another field any time soon. I'd suggest to make this field behave consistently. |
|
Yes @jablan I understand, it will be a bigger refactoring, but given the fact that right now this field is not behaving consistently, should we wait with this PR to avoid any further confusion? Or maybe make it explicitly from where user_id actually changes (not from uploads) but thats not a good way... So maybe we can wait for this to be merged until we have clarity on the behaviour of the field? |
| title: translation_details | ||
| properties: | ||
| user: | ||
| description: The user who last updated the translation content |
There was a problem hiding this comment.
I believe we can only phrase it like that if this would be true for all cases, which is currently not the case. So we need to wait with this change.
3 participants
https://memsource.slack.com/archives/C02QV9K8EP5/p1760016489742879