User tests: Successful: Unsuccessful:
JAdapter
does have it's own class loading and file path lookup logic. With the introduction of a DI container which can manage objects this becomes obsolete.
This pr deprecates the classes.
Status | New | ⇒ | Pending |
Category | ⇒ | Libraries |
That type of comment is only needed when you're deprecating the class inheritance (i.e. places we broke the inheritance from JObject). You don't need to explicitly say "as of X class will no longer extend Y" when the parent class is being completely removed, that should be implied.
Roger that.
I have tested this item
Status | Pending | ⇒ | Ready to Commit |
RTC
Status | Ready to Commit | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2018-06-18 02:52:07 |
Closed_By | ⇒ | mbabker | |
Labels |
Added:
?
|
I have tested this item✅ successfully on ee5b18a
This comment was created with the J!Tracker Application at issues.joomla.org/tracker/joomla-cms/20714.