Details
-
Story
-
Resolution: Done
-
High
-
None
-
None
-
Sprint 3
-
5
Description
Following discussion, if simplification spike proves to be a good direction, we'll have to move it into standard development path.
This includes:
- developing in the open ezplatform repository.
- cleaning up the code.
- any other things related to reach standard quality which was not done during the prototyping.
Attachments
Issue Links
- relates to
-
EZEE-1728
eZ Platform 2 Architecture Simplification
-
- Development
-
1.
|
Unify a way how Symfony Forms are used |
|
Closed | Unassigned |
2.
|
Move business logic from controllers to separate, reusable layer |
|
Closed | Unassigned |
3.
|
Make sure class/method names are consistent |
|
Closed | Unassigned |
4.
|
Add tests and perform cleanup in DataMapper and Transformer classes |
|
Closed | Unassigned |
5.
|
Remove hardcoded default values (expose configuration) |
|
Closed | Unassigned |
6.
|
Coding standards (PHP-CS-Fixer configuration) |
|
Closed | Unassigned |
7.
|
Reuse Tabs feature (ie. dashboard) |
|
Closed | Unassigned |
8.
|
Prepare eZ Platform Meta 2.0 branch |
|
Closed | Unassigned |
9.
|
Update code to match PHP 7.1 spec. |
|
Closed | Unassigned |
10.
|
Create sass base structure |
|
Closed | Unassigned |
11.
|
Move React modules into a separate repository |
|
Closed | Unassigned |
12.
|
React modules code doc and dev examples doc |
|
Closed | Unassigned |
13.
|
Reuse React same components across separate modules |
|
Closed | Unassigned |
14.
|
Update missing default translations so we can generate XLIFF |
|
Closed | Unassigned |