Work Package #48275

TypoScript consistency

Added by Aske Ertmann over 8 years ago. Updated about 8 years ago.

Status:
New
Priority:
Should have
Category:
General / Project
Target version:
Start date:
2012-08-16
Due date:
% Done:

67%

Estimated time:
(Total: 0.00 h)

Description

TypoScript consistency

  • Target Audience: integetors who want to implement sites
  • Responsible: Sebastian Kurfürst
  • Implemented by: the whole Neos Team
  • Amount: not estimatable, not paid, done on voluntary basis
  • Version: must have for 1.0
  • Planned Implementation Timeframe: continuous work

Motivation

In order to get a consistent experience and logical understanding of TypoScript we need to improve some of the concepts

Goal

To achieve a consistent and flexible TypoScript implementation that would don't need to change much in the future

Deliverables

  • Improved FlowQuery #48278, #48280
  • Per-Site instead of Per-Node TypoScript #48321
  • Value / TS Object Interoperability #48359
  • Kill processor classes, change processor syntax #48361
  • (maybe) rename "matcher" to "if" #48362
  • (maybe) implement declarative configuration per TYPO3CR Node #48363

Subtasks

Task #48276: Put site root node into Eel contextResolvedChristian Müller2013-05-16

Actions
Task #48278: Add "Find" FlowQuery operationNew2013-05-16

Actions
Task #48280: Add Eel expression support for node identifiersResolvedChristian Müller2013-05-16

Actions
Task #48321: Drop support for node based TypoScript filesResolvedChristian Müller2013-05-17

Actions
Task #48479: make priorities in @position before/after consistentResolvedSebastian Kurfuerst2013-05-23

Actions
Task #49014: Detect prototype copying leading to a loopNew2013-06-11

Actions
Task #52433: allow "this" in all TypoScript objects to reference other propertiesResolvedSebastian Kurfuerst2013-10-01

Actions
#1

Updated by Sebastian Kurfuerst over 8 years ago

  • Subject changed from [WIP] TypoScript consistency to TypoScript consistency

Also available in: Atom PDF