[#20640] - [4.0] Introduce model interfaces
- Fixed in Code Base
- 8 Jan 2019
- Medium
- Build: 4.0-dev
- # 20640
- Diff
- Digital-Peak:j4/model/interfaces
- Pending Hound Hound is busy reviewing changes... Details
User tests: Successful: Unsuccessful:
As discussed last year at JDayUK, it would be nice to have some model interfaces (probably also for controller and views on some point). This pr adds the following new interfaces for the existing MVC models (except the admin model):
- ModelInterface
- StateModelInterface
- DatabaseModelInterface
- ListModelInterface
- ItemModelInterface
Backwards compatibility
The ItemModel requires now a getItem function. This function needs a $pk argument which is defaulted to null.
More changes
The state code of the BaseDatabaseModel got moved into a new subclass StateModel and the legacy getInstance stuff into a legacy trait. So we have stuff a bit better separated.
| Status | New | ⇒ | Pending |
joomla-cms-bot
- | Category | ⇒ | Administration com_content com_contenthistory Libraries |
| Labels |
Added:
?
|
||
I'm holding on merging this for now with all the entity work going on. I don't want to make a semi-major change like this if we can get the entity stuff into 4.0 - if we don't have time to get it in then clearly this is fine and can be merged
I do not understand why the entities work does block this one as it is basically a new branch of classes starting from the BaseModel or not?
As GsoC is finished, what's the state of the Entities project?
| Labels |
Added:
?
|
||
OK Now i've compromised with webservices to use legacy MVC time to resurrect this :)
rebooted drone: http://ci.joomla.org/joomla/joomla-cms/13548
rips is happy now
| Status | Pending | ⇒ | Fixed in Code Base |
| Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2019-01-08 22:54:58 |
| Closed_By | ⇒ | wilsonge |
Thankyou for being patient with this! :)
Added a
FormBehaviorTraitto remove the redundant code between the FormModel and ListModel.