For fields like xxx2Many the changed values are operation to apply on the
existing value. So we must be sure to have loaded the value.
issue9730
review314491002
Setting a reference field with an on_change in an editable list won't set the
correct value for the model selection. We should do like in tryton and call
set.
issue9083
review297071003
The issue8312 was to strict by its usage of Group._context as it misses the
context_model, the parent context or the _datetime keys.
Instead we introduce a second type of context which provides the same context
but without the session part.
issue8463
review255831002
Those calls can be triggered by event like focus-out. So to ensure a correct
order of the flow, we must defer the processing of the result.
issue8482
review273571002
We preload the first field of the first row if needed. This should ensure that
the following records are also loaded.
And we do not call load if the field is already loaded to avoid to create a
promise.
issue8199
review265411002
The display must be run before the callback linked to the promise of
save_current. And save_current must return a promise with the same state as
the save promise.
Also save should not reject with the exception to avoid jQuery warning.
issue8338
review265421002
In contrary to One2Many, Many2Many can not be modified when they are readonly.
But Many2Many inherit from One2Many so we must exclude them explicitly from
the test.
issue8323
review275371002
fieldnames is already converted to an Array so sending it's keys will send
the Array indexes but the server expects the field names.
issue8280
review249291003
* Add resources method to ModelStorage
* Support badge on icon
* Display unread and total of notes
* Add two extra colors for icon
issue8122
review70561002
Object.getOwnPropertyDescriptor fails if the value is undefined and the method
can return null if there is no such property.
So we must ensure that the value is a Group (which means an Array).
issue8136
review53561002
The current implementation of Group.sort is not correct because it does not
guarantee to replace all the records if the ordered list does not contain all
the existing records. So it is better to use the standard Array.sort method.
Also the search_count should not be updated when doing a search only for ids
as the number of record does not change.
issue8042
review50731002
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
We can not rely on the screen linked to the group to provide this information
because if the group is the value of a One2Many inside a One2Many, the screen
is shared between multiple records and so only one record is linked to the
screen. So when the top record is validated all the records not linked to the
screen may be considered invalid because the exclude_field will not be
excluded from the validation.
issue7715
review46651002
Cédric Krier