Project

General

Profile

Actions
Copy link

Feature #91865

closed

ConfigurationProcessor

Added by Nikita Hovratov almost 4 years ago. Updated over 2 years ago.

Status:
Rejected
Priority:
Should have
Assignee:
-
Category:
Code Cleanup
Target version:
Candidate for Major Version
Start date:
2020-07-24
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

It is very tedious sometimes to search for all the possible configuration for content elements.
The only place to look for is the documentation. The problem is the documentation is not up to date all the time and some important info like default values are missing sometimes or are wrong.

Right now all the configuration is scattered around the code and there is no central place where it is defined. This causes a lot of "isset" checks or if there aren't any a lot of PHP notices.

With this approach the possible configuration should be defined in one place (class). Types like INT, STRING, BOOL have to be declared in order to validate the users input.

Result is cleaner code, as there are less checks and config is not evaluated at place, but beforehand by the ConfigurationProcessor.

Actions
Copy link

Also available in: Atom PDF