Contributors mailing list archives
Re: Migration to Odoo 14: replacing size attribute of Char fieldby
Tecnativa. S. L., Pedro M. Baeza
The warning is from Odoo, not from linters, so #noqa is not valid.
El vie., 21 may. 2021 14:52, Graeme Gellatly <email@example.com> escribió:
I think if the use case is valid and no convenient good alternative exists then the easiest solution is# noqawith a note.On Sat, May 22, 2021 at 12:16 AM Dominique k <firstname.lastname@example.org> wrote:how about api.onchange ?it would work on form modification.--On Fri, 21 May 2021 at 6:57 PM, Simone Rubino <email@example.com> wrote:Hi all,I am migrating some modules to version 14 following https://github.com/OCA/maintainer-tools/wiki/Migration-to-version-14.0 but there is:Remove size=X attribute in Char fields, as it's no longer valid for restricting the size of the strings.that I don't know how to satisfy.The attribute size=X still works fine in Odoo 14 with also the UI limitation so I believe this comes from https://github.com/odoo/odoo/blob/1c39814bd729cc08882f1545c7d88b0592e63f9a/odoo/fields.py#L1608 but as far I can see, it has always been deprecated (at least from https://github.com/odoo/odoo/commit/524bb0a52027ec81245750bb5f0a9e5320faf922), so is there any reason for this to be explicitly mentioned in Odoo 14 migration?I know I could add an `api.constrains` but this looks to me like overkill since I believe constraints should be used for more complex conditions.Moreover: `api.constrains` does not add any limitation in the UI, so it is not as user-friendly as the attribute size=X that does not allow the user to input more than X characters.I should then add also something in every view showing the Char field (hopefully just an option for the Char widget), but it still seems too much work for such an easy requirement.This said, what is a valid alternative to the size=X attribute?Thanks,Simone Rubino
AGILE BUSINESS GROUP SAGL, Simone Rubino