-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[4.0] Update the com_content manifest file #21817
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
Conversation
| <filename>controller.php</filename> | ||
| <folder>controllers</folder> | ||
| <folder>elements</folder> | ||
| <folder>Controller</folder> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
missing
filename content.xml
|
other than the missing file it looks ok to me would be good to get another check though |
| <folder>models</folder> | ||
| <folder>Model</folder> | ||
| <folder>Service</folder> | ||
| <folder>Table</folder> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
if i'm not wrong there is no Table folder
|
Added also media folder. |
|
I am wondering if we even need these manifest files for core components and with the move of media files if they should be in the manifest either |
|
Yes the extension manifests should be in place. Technically, we don't need them, but the core package shouldn't be taking liberties as it relates to extension structure that a distributed extension can't. |
|
And the media folder? The same? @laoneo did you have to create this manually - if so I am happy to takeover so you can concentrate on developer stuff |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think we need the media tag - we aren't shipping a media folder with the extension as it's all baked into core (especially now with the es6 stuff) - so I'd leave that as it is. Otherwise LGTM
|
For me it reflects the installed state of an extension which includes the media folder and com_content has a media folder. From my understanding an extension dev should be able to take it as example and the manifest with the media folder is part of it. I can remove it if you really want but I think it is not a bad idea to leave it in. @brianteeman yes I'm doing them by hand. If you want you can take over the task when we get this one merged. But I would wait about the agreement of the media folder. |
|
When you decide on media let me know and i can get this done |
|
Not convinced about the media tag - but not sceptical enough to block progress here |
Based on the work by @laoneo in joomla#21817 Code review only
Pull Request for pr #21790.
Summary of Changes
As #21790 revealed, the manifest files in core are out of sync. Before I'm going to fix all of them I would like to get some feedback what all needs to be adapted.
Beside the folders I would also change the compatibility version and the version of the extension itself. Anything else?