TLWebdesign/upgrade-checklist
1
0
Fork 0
forked from joomla/upgrade-checklist
Code Pull Requests Activity

Update Moving from J to Namespace.md

Browse Source
This commit is contained in:
Tom van der Laan 2024-01-30 11:58:51 +00:00
parent 56eb30d08f
commit b3156128c6
1 changed files with 20 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
Moving from J to Namespace.md
View File

@ -1,16 +1,29 @@
Class map in J3:
## Class map in J3:
[https://github.com/joomla/joomla-cms/blob/3.10.12/libraries/classmap.php]
Class map in J5:
## Class map in J5:
[https://github.com/joomla/joomla-cms/blob/5.0-dev/plugins/behaviour/compat/src/classmap/classmap.php]
How to handle Classes that have no new counterparts like:
## How to handle Classes that have no new counterparts like:
- JError
- JError::raiseError() should be replaced with native exceptions.
- JError::raiseWarning() and JError::raiseNotice should be replaced with calls to application's enqueueMessage() method to display warnings/notices.
### JError
- JError::raiseError() should be replaced with native exceptions.
- JError::raiseWarning() and JError::raiseNotice should be replaced with calls to application's enqueueMessage() method to display warnings/notices.
More info on backwards compatible issues:
This would mean you wrap your code in a try catch block and return the error. Someting like this:
```
try {
// Your code here;
} catch (\RuntimeException $e) {
throw new \Exception($e->getMessage(), 500, $e);
}
```
Or you would manually report an error back like this:
```
throw new \Exception(Text::_('Your error message here'), 500);
```
## More info on backwards compatible issues:
[https://docs.joomla.org/Potential_backward_compatibility_issues_in_Joomla_4]