This repository has been archived by the owner on May 4, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 13
/
ChangeLog
95 lines (95 loc) · 3.36 KB
/
ChangeLog
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
[BUGFIX] Required has no effects for files
Resolves: #71668
FollowUp 71028 use fieldName as argument
[Bugfix] use fieldName as argument
Resolves #71028
[BUGFIX] Create overrides directory if existing models are extended
Resolves: #71611
[BUGFIX] Prevent error on existing files without namespace
[BUGFIX] Add 'foreign_sortby' for relations to records with sorting
If 'foreign_sortby' is set related records are sorted correctly
upon fetching.
Resolves: #68694
[TASK] Use PSR-2
Resolves: #70313
[BUGFIX] Repository should default to respect sorting
If a model has sorting the repository should respect it.
Set the defaultOrderings-property.
Resolves: #49579
[TASK] Add renderType for select-fields
Resolves: #71344
[TASK] Remove new action test
The newAction in controllers is empty and thus
can't be tested
[BUGFIX] Fix regex for smd url
Resolves: #70031
Make relations sortable
Resolves: #68689
[TASK] Add client side validator
Resolves: #59379
[FEATURE] Confirm overwrite
Resolves: #67232
[TASK] Enable renaming of vendor
Resolves: #70818
Add more properties to fixture tests
Update version to 7.6
Use correct typoscript key for backend modules
Resolves: #69954
[BUGFIX] Use PSR-7-based Routing for Backend AJAX Requests
In TYPO3 CMS after 7.5.0 with commit
Introduce PSR-7-based Routing for Backend AJAX Requests
the way for doing backend AJAX-requests changed.
Use the TYPO3.settings.ajaxUrls-identifier depending on version.
Resolves: #70808
[TASK] Implement traits
Resolves: #63095
Remove renderMode attribute for flashMessages
Resolves: #69465
Use new vendor name in fixture extension
Update to version 7.5-dev
Resolves: #70188
[BUGFIX] Fix wrong jQuery selectors
When adding relations in the modeler the selector
for the uid of the relation was wrong leading to
wrong wire configuration, when the extension is
loaded again and to wrong mapping of relation source
Remove unused Exception translation code
Use getAccessibleMock instead of getMock($this->buildAccessibleProxy...)
Make use of PHP 5.5 class name resolution
Remove obsolete class properties
Refactor Tests
[TASK] Remove inject methods
[TASK] Refactoring to reduce dependencies
[TASK] Rename boolean and integer type hints
Resolves: #58230
[TASK] Use correct RTE configuration
Resolves: #69603
[TASK] Add a warning if mapping to TYPO3 tables
Resolves: #69656
[BUGFIX] Follow up to #69635
Resolves: #69635
[BUGFIX] Wrong class name when renaming extension
Resolves: #69635
[TASK] Prepend Vendor name in registerPlugin
Resolves: #69613
[TASK] Refactor tests and add configuration for TravisCI
Use special composer configuration to enable functional tests
in a local -Build folder
Tests will be reorganized since most unit tests are in fact
functional tests since they depend on objects which are generated
by the ExtensionBuilder
Resolves: #69615
[TASK] Update documentation template
[FEATURE] Enable optional generation of documentation-template
Resolves: #64502
[TASK] Use array for template rootpaths
Fix: #66306
[TASK] use correct registerAjaxHandler
[TASK] Implement 7.4 compatibility
Fixes: #69444
[BUGFIX] Removed attribute for be.container in CMS 7.4
[TASK] Typoscript configuration per plugin and per module
!! Can be a breaking change, since typoscript configuration
is based on extkey_pluginkey now.
Resolves: #62105
git log 2e03533e..HEAD --pretty=format:"%s%n%b%n" | grep -v "^$" | grep -v "Tested-by\|Reviewed-by\|Change-Id\|Reviewed-on\|Release" > ChangeLog