Merge lp:~christophe-chauvet/openobject-client/trunk-save-readonly-field into lp:openobject-client
Status: | Rejected |
---|---|
Rejected by: | tfr (Openerp) |
Proposed branch: | lp:~christophe-chauvet/openobject-client/trunk-save-readonly-field |
Merge into: | lp:openobject-client |
Diff against target: |
62 lines (+11/-4) 2 files modified
bin/options.py (+7/-2) bin/widget/model/record.py (+4/-2) |
To merge this branch: | bzr merge lp:~christophe-chauvet/openobject-client/trunk-save-readonly-field |
Related bugs: |
Reviewer | Review Type | Date Requested | Status |
---|---|---|---|
Christophe Simonis (OpenERP) | Disapprove | ||
Christophe CHAUVET (community) | Needs Resubmitting | ||
Nhomar - Vauxoo (community) | Needs Resubmitting | ||
Review via email: mp+30989@code.launchpad.net |
Description of the change
Hi
I implement a great feature that all integrators wants, the possibility to save a readonly field, specialy when a result is return by a on_change.
I keep a backward compatibility (not activate by default)
if argument --save-readonly (or -r) is called, the readonly file can be save.
this argument can be save on the .openerprc file on cient section
[client]
save_readonly = True
Regards,
Unmerged revisions
- 1432. By Christophe CHAUVET
-
[IMP] use the new option name to save all fields
- 1431. By Christophe CHAUVET
-
[IMP] Rename option as suggested, use --always-save instead of --savee-readonly
- 1430. By Christophe CHAUVET
-
[ADD] New options can save the readonly field or if field have an attrs readonly enable
now on_change return result on a readonly field can be saved
I didn't try it yet but is a great feature!!!!....
And I think is not a big improve, i think is a bug, it should be merged.... approved for me... ;-)
I will try and i will give some information......