-
-
Notifications
You must be signed in to change notification settings - Fork 3.7k
[4.0] Rework CMS Application Interface tree #28313
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
8163a49 to
27c5e18
Compare
27c5e18 to
be5b3c7
Compare
|
Increasing priority as this is a partial fix to a beta blocker. This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/28313. |
|
Added back the beta-blocker label since the issue tracker has removed it, it seems, when priority was changed. |
be5b3c7 to
64ab7f8
Compare
|
Added a different interface for the stuff in the web interface - aim is we have CMSApplicationInterface which is for all application clients (mainly think cli plus web clients) then CMSWebApplicationInterface which covers the additional methods for web requests (api + html etc) |
64ab7f8 to
53410d4
Compare
laoneo
left a comment
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.
Nice one!!
|
Merging this as a first point. We may need to tweak things going forward |
Pull Request for Issue #24587 (only part).
Summary of Changes
Start reworking the CMS Application Interfaces onto the new interfaces introduced in the framework
Testing Instructions
Mainly Code review but you can check the Application still works without throwing missing function fatals (but that is the CIs job)
Documentation Changes Required
Yup - although there shouldn't be any breaks the interfaces need to be documented