This project is mirrored from git://git.typo3.org/Packages/TYPO3.CMS.git. Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
  1. 03 Aug, 2021 1 commit
  2. 22 Jul, 2021 1 commit
  3. 27 Apr, 2021 1 commit
  4. 17 Apr, 2020 1 commit
  5. 15 Apr, 2020 1 commit
  6. 14 Apr, 2020 1 commit
  7. 30 Dec, 2019 1 commit
  8. 18 Dec, 2019 1 commit
  9. 23 Aug, 2019 1 commit
  10. 15 Mar, 2019 1 commit
  11. 11 Sep, 2018 1 commit
  12. 02 Sep, 2018 2 commits
  13. 26 Apr, 2018 1 commit
  14. 25 Apr, 2018 1 commit
  15. 13 Jan, 2018 1 commit
  16. 30 Nov, 2017 1 commit
  17. 27 Nov, 2017 1 commit
  18. 04 Oct, 2017 1 commit
    • Benni Mack's avatar
      [!!!][TASK] Use native trigger_error and ErrorHandler for deprecations · 95b13dca
      Benni Mack authored
      The native PHP way of triggering deprecations by a framework or
      applications is done via
      `trigger_error($deprecationMessage, E_USER_DEPRECATED)`.
      
      Previously, TYPO3 used `GeneralUtility::deprecationLog()` and
      similar methods to generate a custom deprecation log, however it's
      more flexible to use native logging through TYPO3's ErrorHandler.
      
      This solution centralizes the way to configure the place if and
      how deprecation logs should be written to various log destinations.
      
      This also changes the way how deprecated methods, arguments and classes
      are handled.
      
      The new way to deprecate code in TYPO3 is done via
      `trigger_error()`, the @deprecated annotation within a method only
      exists now for IDE support, but is not reflected anymore for the
      logging message.
      That's why the @deprecated annotation does not contain
      a description anymore.
      
      The methods
      GeneralUtility::logDeprecatedFunction()
      GeneralUtility::deprecationLog()
      GeneralUtility::getDeprecationLogFileName()
      GeneralUtility::logDeprecatedViewHelperAttribute()
      
      are marked as deprecated from now on.
      
      The configuration option $TYPO3_CONF_VARS[SYS][enableDeprecationLog]
      is removed.
      
      Deprecation messages can now be activated by adding
      the E_USER_DEPRECATED constant to the respective values in
      
      $TYPO3_CONF_VARS[SYS][errorHandlerErrors]
       (so exceptions are handled by the TYPO3 error handler)
      $TYPO3_CONF_VARS[SYS][syslogErrorReporting]
       (so exceptions are put into GeneralUtility::sysLog)
      $TYPO3_CONF_VARS[SYS][belogErrorReporting]
       (so exceptions are put into sys_log DB table)
      $TYPO3_CONF_VARS[SYS][exceptionalErrors]
       (so exceptions are thrown on a deprecation)
      
      Deprecations will still go into GeneralUtility::devLog(),
      if deprecations are activated via the "errorHandlerErrors" option.
      
      Tests which test explicitly for deprecated code is moved into
      Tests/UnitDeprecated, to ensure that the deprecated code is not
      throwing an exception.
      
      Resolves: #82438
      Releases: master
      Change-Id: I6ef9a642d179001f0484c4c7678e0bec12284faf
      Reviewed-on: https://review.typo3.org/54015
      
      Reviewed-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      Tested-by: Susanne Moog's avatarSusanne Moog <susanne.moog@typo3.org>
      Tested-by: default avatarTYPO3com <no-reply@typo3.com>
      Reviewed-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      Tested-by: Christian Kuhn's avatarChristian Kuhn <lolli@schwarzbu.ch>
      95b13dca
  19. 12 May, 2017 1 commit
  20. 28 Mar, 2017 1 commit
    • Wouter Wolters's avatar
      [TASK] Streamline return tags in phpdocs · eb049dba
      Wouter Wolters authored
      The TYPO3 Core currently has no guidline how to handle phpdoc
      comments regarding @return annoations related to "void" and "null".
      
      In practice, these annotations have no additional value if no additional
      documentation is given.
      
      With this change, the php-cs-fixer will remove any unnecessary linebreaks
      within the comments above the @return annotation, as well as remove completely
      empty phpdoc comments because the @return annotation is removed.
      
      Please be aware, that once PSR-5 is accepted, this coding standard
      within the TYPO3 Core will change again, where there are currently
      some further proposal details like inheritance information.
      
      Resolves: #80454
      Releases: master
      Change-Id: Ie969d720684c0a75919fe5addd1c36ef5b12eb04
      Reviewed-on: https://review.typo3.org/51686
      
      Reviewed-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Tested-by: Nicole Cordes's avatarNicole Cordes <typo3@cordes.co>
      Reviewed-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      Tested-by: Benni Mack's avatarBenni Mack <benni@typo3.org>
      eb049dba
  21. 01 Feb, 2017 1 commit
  22. 01 Dec, 2016 1 commit
  23. 08 Nov, 2016 1 commit
  24. 26 Oct, 2016 1 commit
  25. 25 Oct, 2016 1 commit
  26. 30 Aug, 2016 1 commit
  27. 22 Aug, 2016 1 commit
  28. 09 Jun, 2016 1 commit
  29. 25 May, 2016 1 commit
  30. 07 Apr, 2016 1 commit
  31. 04 Mar, 2016 2 commits
  32. 01 Mar, 2016 1 commit
  33. 28 Jan, 2016 1 commit
  34. 22 Jan, 2016 1 commit
  35. 08 Jan, 2016 2 commits
  36. 28 Oct, 2015 1 commit
  37. 08 Oct, 2015 1 commit