This project is mirrored from https://git.typo3.org/typo3/typo3.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 .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer.
Last successful update .
- 29 Jul, 2021 1 commit
-
-
This change uses RelationHandler for foreign_table / allowed and MM in BackendUtility::getProcessedValue in a consistent way. In addition, the RelationHandler now fetches the full record by default and adds this to the processed array, making fewer queries to the database by fetching each record fully directly. Some bugs are fixed with that: * FAL images (as in all inline fields) in list module now have the correct order * Fewer DB queries when fetching relations in Group field in FormEngine Setting the option in RelationHandler to fetch all fields by default avoids unneeded calls in general when fetching the records. Resolves: #94651 Releases: master Change-Id: I8261a0c2657b9b71ae7cdc686ee43eaa7461c8b6 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70117 Tested-by:
core-ci <typo3@b13.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 15 Apr, 2020 2 commits
-
-
TYPO3's PHP-CS-Fixer configuration is adapted to move towards the PSR-12 standard by unifying the new statement and adding proper braces argument methods and arguments. Resolves: #91026 Releases: master Change-Id: If5eb945e18fb4a2330e3c9eeaf90134126638079 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64163 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com>
-
With this patch, the header comment of php files is automatically added by the php-cs-fixer, which guarantees that its format and place of occurrence remain the same in all files. Files that are copied over from other projects are excluded. Furthermore, files that are kind of inspired by other projects also get the same header comment but may have a second, additional comment explaining its origin. Used command: bin/php-cs-fixer fix --config=Build/php-cs-fixer/header-comment.php Releases: master Resolves: #91024 Change-Id: I5a040517e0fbde6e5a27d589bf2f222078326dc8 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64159 Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Benni Mack <benni@typo3.org>
-
- 14 Apr, 2020 1 commit
-
-
This change adds two changes 'blank_line_after_opening_tag' => true, 'single_trait_insert_per_statement' => true, to our PHP-CS Fixer configuration, adopting more rules related to PSR-12. Resolves: #91020 Releases: master Change-Id: I180b2cbceb077911bddeb42d9f131e5b32244ed2 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/64158 Tested-by:
Josef Glatz <josefglatz@gmail.com> Tested-by:
Oliver Bartsch <bo@cedev.de> Tested-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Josef Glatz <josefglatz@gmail.com> Reviewed-by:
Oliver Bartsch <bo@cedev.de> Reviewed-by:
Alexander Schnitzler <git@alexanderschnitzler.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 24 Oct, 2019 1 commit
-
-
Class \PHPUnit\Framework\TestCase provides many assertion methods that can be called statically and dynamically in the context of tests. Sebastian Bergmann states that neither using $this nor self/static is right or wrong. There are two reasons to use self/static however. First of all IDE's like PhpStorm support code inspections that tell you to not call static methods dynamically and therefore make your code look like a christmas tree. Secondly, there is a rule for php-cs-fixer that can take care of the initial change and which helps sticking to one specific format, unifying the code style overall. Releases: master Resolves: #89499 Change-Id: Ib4a43a94a0df220b052b88b3c3e37e716560e996 Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/62095 Reviewed-by:
Oliver Klee <typo3-coding@oliverklee.de> Reviewed-by:
Manuel Selbach <manuel_selbach@yahoo.de> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Oliver Klee <typo3-coding@oliverklee.de> Tested-by:
TYPO3com <noreply@typo3.com> Tested-by:
Manuel Selbach <manuel_selbach@yahoo.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de>
-
- 14 Jan, 2019 1 commit
-
-
This drops TCA type=group with internal_type=file and internal_type=file_reference handling. This patch is rather huge since detail handling of this stuff is spread throughout the core. Additionally, some further methods become unused and oboselete along the way. Most of them - except DataHandler->process_uploads() - have been used internally only and can be safetly dropped, while process_uploads() which has always been part of the externally called API is substituted with a no-op method. Resolves: #87428 Releases: master Change-Id: Ia60b5d0e021b34adf4b4187a5f1fe4475b0070b4 Reviewed-on: https://review.typo3.org/59361 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
TYPO3com <noreply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 11 Jun, 2018 1 commit
-
-
typo3/testing-framework since version 3.8.0 can reset singletons created by makeInstance automatically if $this->$resetSingletonInstances is set to true. This version additionally checks for left over singletons in case that property has not been set and lets tests fail in this case. composer require --dev typo3/testing-framework:^3.8 As advantage, a manual backup of singleton instances within tests is not needed anymore. The patch comes with a set of test case adaptions to cope with this new situation. Change-Id: Ib5f278145e385e32d543541872cf5e1f208fad47 Resolves: #85209 Releases: master Reviewed-on: https://review.typo3.org/57169 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Joerg Boesche <typo3@joergboesche.de> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 20 Feb, 2018 1 commit
-
-
Christian Kuhn authored
Similar solutions as in issue #83975 Change-Id: I04c06f0e73f5e7d44f225ad9b60c9cbed1016308 Resolves: #83981 Related: #83975 Releases: master Reviewed-on: https://review.typo3.org/55834 Reviewed-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Tested-by:
Andreas Fernandez <a.fernandez@scripting-base.de> Reviewed-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Tested-by:
Mathias Schreiber <mathias.schreiber@typo3.com> Reviewed-by:
Frans Saris <franssaris@gmail.com> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 14 Feb, 2018 1 commit
-
-
Raise typo3/testing-framework from 2.0.4 to 3.0.0: composer require --dev typo3/testing-framework ^3.0 The new typo3/testing-framework version comes with a change that no longer suppresses E_NOTICE PHP errors by default and lets tests fail that raise them. The static property $suppressNotices in unit test files is set to true for all test cases that currently raise E_NOTICE errors to suppress them on a by-file basis. Further patches should remove this property one-by-one again by fixing the system under test the unit test case handles. Change-Id: I7d44fe3723ce5820a37051ae31f16b2f142ffba6 Resolves: #83889 Related: #83888 Releases: master Reviewed-on: https://review.typo3.org/55697 Reviewed-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
Tymoteusz Motylewski <t.motylewski@gmail.com> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Markus Klein <markus.klein@typo3.org> Tested-by:
Markus Klein <markus.klein@typo3.org>
-
- 28 Jun, 2017 1 commit
-
-
The array key 'uploadfolder' is initialized on a non existing array. It must be initialized on the processed tca array Resolves: #81681 Releases: master, 8.7 Change-Id: Ied776e4b0d0d4c33cf0894a2c4c95ceb6c03bb18 Reviewed-on: https://review.typo3.org/53311 Reviewed-by:
Henrik Elsner <helsner@dfau.de> Tested-by:
Henrik Elsner <helsner@dfau.de> Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 16 Feb, 2017 1 commit
-
-
Change-Id: Ib8b787980d90c686457155cbb6c15cd3cd7c0d61 Releases: master Resolves: #79851 Reviewed-on: https://review.typo3.org/51715 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Jan Helke <typo3@helke.de> Tested-by:
Jan Helke <typo3@helke.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 04 Feb, 2017 1 commit
-
-
As the main test case files are now in subfolders, we need to correct the namespaces. Change-Id: Ie06edc099c5d3e42ff842eded03cde1ddf34c0ca Releases: master Resolves: #79629 Reviewed-on: https://review.typo3.org/51535 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Susanne Moog <susanne.moog@typo3.org> Tested-by:
Susanne Moog <susanne.moog@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 03 Feb, 2017 1 commit
-
-
- Removal of the CMS part from the namespace - Distinguish Classes / Resources For background information see https://decisions.typo3.org/t/testing-framework-extraction-next-steps/50 Change-Id: I3f73baeb16bbef82c9626add063c9edde41b47a6 Resolves: #79518 Releases: master Reviewed-on: https://review.typo3.org/51449 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 03 Jan, 2017 1 commit
-
-
The patch adapts a series of nasty form engine areas to more solid code. The evaluate condition code is rewritten and works much better in flex form scenarios. The suggest wizard and svg tree are much more solid in flex forms. The group element is rewritten towards a better readable and easier to refactor code, dropping method dbFileIcons(). A bunch of issues is resolved along the way. * TCA "default" now works in flex form section container elements * The "displayCond" parser is now strict and throws exceptions on invalid syntax and wrong referenced fields to help debugging faulty display conditions * TCA displayCond on flex fields can now be prefixed with the sheet name and can reference field values from neighbor sheets * TCA displayCond now works with flex section containers * TCA flex section container now throw an exception if select or group fields configure a MM relation - this is not supported * TCA ctrl requestUpdate field is dropped, onChange=reload is now allowed not only on flex form fields, but also on normal columns fields * TCA tree now works as section container element and initializes correctly on new records and new containers * GroupElement rewrite to drop dbFileIcons() * config option maxitems now optional for type=group and type=select and defaults to "many items allowed" * inline now works in "fancy" flex situations with "new" records by handing the final dataStructureIdentifier around * FormEngine no longer loads extJS Change-Id: Id1d081627529cc1502bb198389e5bd69372815cd Resolves: #78899 Resolves: #72307 Resolves: #75646 Resolves: #76637 Resolves: #72106 Resolves: #78824 Resolves: #76793 Resolves: #68247 Resolves: #69715 Related: #78460 Related: #67198 Related: #72294 Releases: master Reviewed-on: https://review.typo3.org/50879 Tested-by:
TYPO3com <no-reply@typo3.com> Reviewed-by:
Benni Mack <benni@typo3.org> Tested-by:
Benni Mack <benni@typo3.org> Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de>
-
- 22 Dec, 2016 1 commit
-
-
Add testing framework component for independent usage Resolves: #79025 Releases: master Change-Id: I23cfd2ed42108d7d80ec776e778a1ac2d5293e55 Reviewed-on: https://review.typo3.org/50125 Reviewed-by:
Oliver Hader <oliver.hader@typo3.org> Tested-by:
TYPO3com <no-reply@typo3.com> Tested-by:
Oliver Hader <oliver.hader@typo3.org> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 16 May, 2016 1 commit
-
-
- Use expectedException() and expectedExceptionCode() instead of deprecated setExpectedException() - Fix a couple of incomplete tests in core/Http section, add some and slightly refactor a bit Resolves: #76159 Releases: master Change-Id: I3333f94494ce76601a61e4b5286cfef982867f8f Reviewed-on: https://review.typo3.org/48091 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Adrian Mot <adrian.mot@gmail.com> Tested-by:
Adrian Mot <adrian.mot@gmail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 24 Mar, 2016 1 commit
-
-
With minimum php7 and after codeception released a patch level that introduced phpunit 5.x support, we can upgrade our phpunit dev dependency to 5.2 along with a patch level upgrade of vfsStream. This phpunit version is a bit more strict, some unclean tests stumble and need fixes: * $this->setExpectedException() needs a string as second argument, all places with $this->anything() or $this->any() to ignore the actual exception string are now substituted with empty string, the tests rely on the timestamp to specify a specific exception. * $aMock->expects()->method('aMethod') now throws exceptions if a method name is specified that is either not mocked in $this->getMock() or that does not exist in the mocked class. This was previously ignored. This change now catches a lot of code smell in our tests :) Change-Id: I546f8f4b3e05b3d643f4ee6be8e1d4c6e23fe083 Resolves: #75264 Releases: master Reviewed-on: https://review.typo3.org/47388 Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 20 Nov, 2015 2 commits
-
-
Resolves: #71738 Releases: master Change-Id: I71edcdb8ed1804bf94479237bd7f6c120420f779 Reviewed-on: https://review.typo3.org/44834 Reviewed-by:
Martin Kutschker <martin.kutschker@ymail.com> Tested-by:
Martin Kutschker <martin.kutschker@ymail.com> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
Resolves: #71726 Releases: master Change-Id: I4a356c8da668acee555149eee9cf56ccdb4dc0ee Reviewed-on: https://review.typo3.org/44822 Reviewed-by:
Andreas Fernandez <typo3@scripting-base.de> Tested-by:
Andreas Fernandez <typo3@scripting-base.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 13 Nov, 2015 1 commit
-
-
Restore support for group type fields with internal type of `folder`. Resolves: #70449 Releases: master Change-Id: I6cfea6c74c003d64fbbbe7d8904420c757f044d5 Reviewed-on: https://review.typo3.org/44700 Tested-by:
Manfred Rutschmann <manfred@dslr-seite.de> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 11 Oct, 2015 1 commit
-
-
The result key vanillaTableTca turned out to be not useful, so it is merged into the processedTca section. All operations use only this section now. Change-Id: I29c2b5cd45c3ef18b4f5d54ebc644603214b0f9b Resolves: #70564 Releases: master Reviewed-on: http://review.typo3.org/43962 Reviewed-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Tested-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-
- 08 Oct, 2015 1 commit
-
-
TYPO3 Release Team authored
In our efforts to achieve a better interoperability with other PHP projects, the PHP code base of the TYPO3 Core switches to the PHP coding guideline standard PSR-2. See http://www.php-fig.org/psr/psr-2/ for more information. Resolves: #70515 Releases: master Change-Id: I734c0d838af157003decfeb5fc0a11dddcb87bf5 Reviewed-on: http://review.typo3.org/43918 Reviewed-by:
TYPO3 Release Team <typo3cms@typo3.org> Tested-by:
TYPO3 Release Team <typo3cms@typo3.org>
-
- 23 Sep, 2015 1 commit
-
-
Protected is the correct visibility for those functions, as given by the base class. Resolves: #64642 Releases: master Change-Id: Ifb5233f391dfa348d1cbf96baf8999f3cda33d63 Reviewed-on: http://review.typo3.org/43511 Reviewed-by:
Nicole Cordes <typo3@cordes.co> Tested-by:
Nicole Cordes <typo3@cordes.co> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Michael Oehlhof <typo3@oehlhof.de> Reviewed-by:
Georg Ringer <georg.ringer@gmail.com> Tested-by:
Georg Ringer <georg.ringer@gmail.com>
-
- 12 Sep, 2015 1 commit
-
-
Resolves: #69731 Releases: master Change-Id: I06bf6fad1096dfc4f2396f5efae265eba9da25e5 Reviewed-on: http://review.typo3.org/43241 Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl>
-
- 08 Sep, 2015 1 commit
-
-
Christian Kuhn authored
tl;dr: This patch makes FormEngine insanely flexible, extensions however should not rely on structures for now, since class names and array content will change. The patch applies a separation of concerns to the FormEngine class structure by extracting the data processing from rendering. As a main goal the render part consisting of container and element classes routed through the flexible NodeFactory only works on data created by the new FormDataCompiler class construct. This makes the FormEngine much more flexible and opens ways to not only use the render part in the context of database driven data, but on anything that is fed to it. This patch creates the main structure for this. The FormDataCompiler class returns a defined array container and elements can work on it. Data is added by single FormDataProvider, which are combined in FormDataGroups. FormDataProvider may depend on each other and a FormDataGroup "knows" its providers and calls them in a dedicated order. For instance, the "FullDatabaseRecord" FormDataGroup first calls a provider that fetches the record defined by uid and table name and a later called provider determines the given record type this record is assigned to, so another provider can then work on TCA to determine the list of record fields to be shown. The FormDataProvider used for the main FormDataGroup are defined in TYPO3_CONF_VARS, so extensions can add and remove their own providers to add or change certain data if needed. This is highly flexible and extensions are able to hook in at a specific position within the provider chain for the main data groups. This construct obsoletes the DataPreprocessor as well as several other side classes. With this patch the main architecture is created and lots of data preparation is transfered already, supported by a high unit test coverage. The FormEngine class itself is removed: The inline ajax entry point is moved to an own controller class, the getMainFields() and friends methods are substituted with FormDataCompiler / NodeFactory combinations and the data gathering is for now parked in a FormResultCompiler class. However, this process is not yet finished and lots of @todo statements are added to the code base to document open ends and to further separate the data handling from the render engine. Especially the IRRE data handling is currently still located within the render engine and makes the whole thing much more complicated than it should be. Lots of detail patches need to follow to bring this code to a level where it belongs to be. Warning: While this patch is already insanely huge touching more than 22 thousands lines of code, lots of loose ends need to be tackled and the API is not final yet. The arrays will be reduced and sharpened during the next weeks, class names may change and structures will change. Change-Id: Ief1769f478373cc26d1bf6c49114258f0dae8355 Resolves: #69568 Releases: master Reviewed-on: http://review.typo3.org/41933 Reviewed-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Tested-by:
Anja Leichsenring <aleichsenring@ab-softlab.de> Reviewed-by:
Florian Peters <fpeters1392@googlemail.com> Reviewed-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Tested-by:
Mathias Schreiber <mathias.schreiber@wmdb.de> Reviewed-by:
Alexander Opitz <opitz.alexander@googlemail.com> Tested-by:
Alexander Opitz <opitz.alexander@googlemail.com> Reviewed-by:
Wouter Wolters <typo3@wouterwolters.nl> Tested-by:
Wouter Wolters <typo3@wouterwolters.nl> Reviewed-by:
Christian Kuhn <lolli@schwarzbu.ch> Tested-by:
Christian Kuhn <lolli@schwarzbu.ch>
-