Task #6564

Move the YAML parser from its own package to within FLOW3

Added by Robert Lemke almost 10 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Should have
Assignee:
Category:
Configuration
Start date:
2010-02-22
Due date:
% Done:

100%

Sprint:
PHP Version:
Has patch:
Complexity:

Description

In order to make FLOW3 self-contained, move the YAML parser to the FLOW3 package and removed the dependency to the YAML package.

Associated revisions

Revision c524f4f0 (diff)
Added by Robert Lemke almost 10 years ago

[~TASK] Removed the YAML package from the Base distribution. Relates to #6564.
[+FEATURE] Added an action "migrate objectmanagerusage" to the flow3 script. Relates to #6562

Revision cfee0bf0 (diff)
Added by Robert Lemke almost 10 years ago

[+FEATURE] FLOW3 (Object): Implemented a static object container which is automatically built. It's essentially a hardcoded version of the autowired and configured object dependencies - just a lot faster. Many tests are still missing, but the version in this commit should be mostly functional. Addresses #3740 and resolves #2123.
[!!!][~API] FLOW3 (Object): Heavily refactored the Object Manager and its tests. The most important change is the removal of the Object Factory whose create() method is now located in the Object Manager. Furthermore, the getObject() method has been renamed to get() and a few minor important API functions within the Object Manager have been modified. This commit also contains a script which allows for semi automatically migrating existing code to the new API (see ./flow3 migrate objectmanagerusage). Resolves #6562
[~TASK] FLOW3 (Configuration): The Configuration Manager and its YAML source now doesn't depend on the YAML package anymore but refers to a YAML parser class within the FLOW3 package. Resolves #6564.

History

#1 Updated by Robert Lemke almost 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r3837.

Also available in: Atom PDF