Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[15.0] move xml-deprecated-tree-attribute to optional checks ? #76

Closed
sbidoul opened this issue Oct 18, 2021 · 8 comments
Closed

[15.0] move xml-deprecated-tree-attribute to optional checks ? #76

sbidoul opened this issue Oct 18, 2021 · 8 comments

Comments

@sbidoul
Copy link
Member

sbidoul commented Oct 18, 2021

Question by @feketemihai on the mailing list

Example: OCA/l10n-romania#173

@feketemihai
Copy link
Member

At least from my side this is quite usefull, so i don't know why this is deprecated but the at least the "string" tag, depending on some views it was easy to show different names, at least where you have one one2many field, but showed in 2 wotkflows, like separate it in customers and suppliers, and use 2 string for the same field. I agreed we can do it with label, but have to check if we have the same effect as the string in tree.

And if it's deprecated, as @pedrobaeza said, than Odoo should not use it no, but we have more than 100 example in the Odoo base code, so from my side i would move it to optional.

@pedrobaeza
Copy link
Member

string attribute of <tree> tag is ignored since a long time AFAIK.

@sbidoul
Copy link
Member Author

sbidoul commented Oct 18, 2021

Can anyone find a reference from Odoo (in docs or source code) about this ?

@moylop260
Copy link
Contributor

@sbidoul
Can anyone find a reference from Odoo (in docs or source code) about this ?

Notice the <!-- deprecated, has no effect anymore -->:

More info about:

@yajo
Copy link
Member

yajo commented Oct 19, 2021

FTR we can add it as optional in any version where it makes sense, as optional checks won't affect CI statuses.

@pedrobaeza
Copy link
Member

But it's clear that the attribute doesn't make sense since a lot, so better to force to remove it for not confusing people about its usefulness, as Odoo has done in its core code with Fekete.

@yajo
Copy link
Member

yajo commented Oct 19, 2021

Ah I see, you mean to move it to optional from required.

Well, if it makes no sense, I'd just leave it as it is indeed.

@feketemihai
Copy link
Member

Good, than i think we can close the issue. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants