Issue 11282

Title
Always return tuple for MultiSelection
Priority
feature
Status
resolved
Nosy list
ced, reviewbot, roundup-bot
Assigned to
ced
Keywords
review

Created on 2022-02-22.18:23:04 by ced, last changed 3 months ago by roundup-bot.

Messages

New changeset 34ecaeef824a by Cédric Krier in branch 'default':
Always return tuple for MultiSelection
https://hg.tryton.org/tryton-env/rev/34ecaeef824a
New changeset 897423a42a3f by Cédric Krier in branch 'default':
Always return tuple for MultiSelection
https://hg.tryton.org/trytond/rev/897423a42a3f
Author: [hidden] (ced) Tryton committer Tryton translator
Date: 2022-02-22.18:23:04

As issue11281 showed, it is easy to forget that MultiSelection can be None.
I think like we do for One2Many and Many2Many we should always return an iterable value. There are no real benefit to distinct empty and null for this field and also the UI can not make the difference.

History
Date User Action Args
2022-03-20 01:45:52roundup-botsetmessages: + msg74637
2022-03-20 01:45:46roundup-botsetmessages: + msg74636
nosy: + roundup-bot
status: testing -> resolved
2022-02-22 18:28:16reviewbotsetmessages: + msg74303
nosy: + reviewbot
2022-02-22 18:25:18cedsetkeyword: + review
reviews: 361021002
status: in-progress -> testing
2022-02-22 18:23:04cedcreate

Showing 10 items. Show all history (warning: this could be VERY long)