The precedence between the + operator and the || makes that the undefined size
is appended to the class string instead of the empty string.
issue9499
review310111002
We implement the same behavior as SQL with NULL which always returns NULL
except for IS operator. So the evaluation has the same result as the search.
issue8615
review290281002
Those branches of the domain should not prevent to compute a proper inverted
domain for the field as the other fields will be fixed later.
issue9200
review311191002
In order to have correct overflow ellipsis, we must stop to use table to align
affix inside a cell. Instead we use flexblox layout to expand the widget and
align the affixes.
Also as now content will be ellipsis, we must provide a title to the buttons.
issue8762
review268231002
This avoids to use negative margin to keep row heigh constant.
And we display the button as block on responsive tree to make it easier to
click on.
issue8761
review286171004
As the optional scrollbar of the treeview will be removed, the dropdown input
may no more be visible. So we must scroll until it is visible.
issue8509
review285581002
The server adds to the definition of the fields, the definition of relation
fields up to specific deep level.
The clients use this relation fields definition to extend the domain parser
with those fields using a dot notation. But those "dotted fields" are not
shown in the search filter to not bloat the popup as it is dedicated to
learning.
In addition, Dict fields are also filled with relation fields coming from the
keys defined in the schema model. As the size can very large, it is possible
to deactivate this feature from the configuration.
issue8293
review259391005
in operator on relation field must use list of ids. So the related rec_name
should be used instead because domain_parser always uses string as value.
issue3540
review271321002
* Add resources method to ModelStorage
* Support badge on icon
* Display unread and total of notes
* Add two extra colors for icon
issue8122
review70561002
Domain inversion on Reference field does not work when using the dotted
notation with a M2O field using child_of or parent_of.
To solve this we correctly compute the localization of child_of leaves when
using the dotted notation (which renders the inverse_leaf function useless).
But we must also ensure that the selection used by reference fields restrict
the choice to the right models.
issue7869
review60441002