Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Joomla 4.0: Move legacy tables to cms tables #12262

Merged
merged 3 commits into from Oct 3, 2016
Merged

Conversation

Hackwar
Copy link
Member

@Hackwar Hackwar commented Oct 2, 2016

This PR moves the JTable classes from the /libraries/legacy folder to /libraries/cms and undeprecates the JTableContent class. I doubt that there will be any UCM in the forseeable future. When it should one day be implemented, we can still deprecate that class again. But until then...

@wilsonge
Copy link
Contributor

wilsonge commented Oct 2, 2016

Would it not be better to move these classes to their respective components rather than the global libraries folder?

@Hackwar
Copy link
Member Author

Hackwar commented Oct 2, 2016

Yes and no, these classes are used not only in their respective component, but all over the place and moving them to their respective component would require all third party extensions to add that folder to the JTable include paths. In order to not change for the sake of change, I would keep it in the libraries folder.

@mbabker
Copy link
Contributor

mbabker commented Oct 2, 2016

Another way to look at it is what tables would be considered part of the "core" data model? Content's pretty specific but the others are part of the global app.

@Hackwar
Copy link
Member Author

Hackwar commented Oct 2, 2016

I'm not saying that I disagree with you that some of these tables belong to their respective component. It is just that I thought the general consensus was to not change for changes sake. This is a change that I consider to be a nice-to-have-but-not-essential, so that in order to keep the change list shorter I wouldn't touch this.

@wilsonge
Copy link
Contributor

wilsonge commented Oct 3, 2016

For the menu I'd put it in com_menu, for content, com_content, for module com_modules.... I mean I'm not fixed on it. But I'd assume that was the idea behind them going into legacy

@wilsonge
Copy link
Contributor

wilsonge commented Oct 3, 2016

I'm not set on that however. If you both think moving them to libraries is better - let's go with it :)

@mbabker
Copy link
Contributor

mbabker commented Oct 3, 2016

If I wanted to be disruptive I'd move JTableContent to the component and leave the rest in the libraries. But that's being disruptive for minimal gain.

With the current data model in core, the concepts of categories, menus, and modules are all global things and are not isolated to a single component (their management is exposed through a component though). So those table classes are rightfully part of the libraries.

@wilsonge wilsonge merged commit e051097 into joomla:4.0-dev Oct 3, 2016
@wilsonge wilsonge added this to the Joomla 4.0 milestone Oct 3, 2016
@Hackwar Hackwar deleted the j4table branch April 27, 2019 07:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants