[16.0][IMP] Make base_external_system easily extendable#414
[16.0][IMP] Make base_external_system easily extendable#414
Conversation
4790a4f to
daa8398
Compare
5d9e8da to
d9aecbe
Compare
|
@thomaspaulb I took up your comments, please look again |
d9aecbe to
e8222e9
Compare
| Changelog | ||
| ========= | ||
|
|
||
| Version 16.0.1.0.0 |
There was a problem hiding this comment.
Given all the major breaking changes done here, should they also be explained with a 16.0.2.0.0 changelog comment, with a rationale and a migration path? If someone had made custom dependent modules that add fields on base.external.system, this will now stop working and someone will need to redo the customization in a new way.
There was a problem hiding this comment.
Ok sorry I'm talking nonsense here, it's not base.external.system that went to become an AbstractModel. Still, I would appreciate an explanation why this is better, if only to be able to review better, and for users to understand.
ceae1a5 to
bad61bb
Compare
This module will be extended with modules to connect to http systems, with additional modules to use oauth authorization.
bad61bb to
1b0b97b
Compare
|
@thomaspaulb @ntsirintanis Because of the change (even if remote) that somebody might have extended this module somewhere in a way that is not compatible with these changes, and because this is not fully plugin-compatible, I will close this, but will implement the changes in the migration to 18.0. |
|
The 18.0 migration is here: #447 |
This module will be extended with modules to connect to http systems, with additional modules to use oauth authorization.
This code is running in production at several customer sites already, together with additional modules for which PR's will follow.