User tests: Successful: Unsuccessful:
deprecate $app
property in FieldsPlugin
only deprecation > code review
check fields plugin still working
Please select:
Status | New | ⇒ | Pending |
Category | ⇒ | Administration com_fields |
Labels |
Added:
PR-5.4-dev
|
I have tested this item ✅ successfully on 7b55457
we need to do better than this. Instead of adding an exception why not fix it. I was taught by @nibra that when we deprecate something we should stop using it in the core at the same time.
@brianteeman In general that's right, but here we need the exclusion due to the b/c code:
$app = $this->getApplication() ?: $this->app;
The ?: $this->app
part has to be kept for b/c until Joomla 7, and this part causes the PHPstan complaint.
But then it would be better to add a phpstan ignore on that line.
But then it would be better to add a phpstan ignore on that line.
@laoneo I don't know. Maybe yes. As it is a relative new thing that we do not ignore PHPstan in CI, we don't have much practice with that yet. Up to now we were using the baseline file to ignore errors and as a task list.
I think we should discuss that and find a common way in the maintainers team.
Shouldn't there be some documentation explaining why this is being deprecated
Shouldn't there be some documentation explaining why this is being deprecated
In future it is no longer supported by CMSPlugin #38060
joomla-cms/libraries/src/Plugin/CMSPlugin.php
Line 163 in 108662f
that isnt a why? and its not in the accompanying manual entry
Status | Pending | ⇒ | Ready to Commit |
RTC as the previous human tests are still valid. There was only a change on the PHPstan baseline file after that and a clean branch update.
To me the joomla/Manual#488 documentation PR looks complete.
Labels |
Added:
RTC
|
✅ Final test before merge, JBT graft full package
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2025-08-09 18:34:28 |
Closed_By | ⇒ | muhme |
Thank you @heelc29 for your contribution. Thank you @brianteeman for support. Thank you @ceford and @laoneo for testing.
I have tested this item ✅ successfully on 7b55457
Just a thought: would it be better to use a local $language variable:
$language = $app->getLanguage()
and then use that in the loops. Otherwise, this looks OK to me.
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/45695.