* Cédric Krier [2018-12-11 18:26:17]: > > Cédric Krier <firstname.lastname@example.org> added the comment: > > Indeed we already do such transformation on some fields. E.g. we > remove the non-significant zero (and trim space) on numeric; we > transform text into int for Many2One, we recompute sequence field. I think you're confusing the value and the way the value is displayed. In case of char data they're both the same, while it's not the case when the data is a relation, a number or an order relationship. > In many char/text fields, trailing spaces have no signification for > the user. Usually it's the case but sometimes it might not be it. > I would not activate on Party.name because it is too much special > but I think it should on almost all other names, If party.name is an exception then trim should default to True for fields.Char. Yet I don't think it's a good idea because it breaks the principle of least surprise: users and developers expect that the data they filled will be saved as-is. > codes, numbers and description. I agree that it can be useful for those fields though.
|2018-12-12 10:12:32||nicoe||set||recipients: + ced, timitos, yangoon, pokoli|
|2018-12-12 10:12:32||nicoe||link||issue7914 messages|
Showing 10 items. Show all history (warning: this could be VERY long)