TYPO3.Flow

I like the concept. As for date formatting, this needs to be configurable. Since the handler could find out about the types of the properties used, it could look for type-specific information in the pattern. E.g. like this:

uriPattern:    'posts/{post}'
defaults:
  '@package':    Blog
  '@controller': Post
  '@action':     show
routeParts:
  post:
    options:
      pattern: '{date format:Y-m-d}/{title}'

Karsten Dambekalns wrote:

As for date formatting, this needs to be configurable.

Yes, but I'm unhappy about yet another syntax

{date format:Y-m-d}

pattern: '{date.year}-{date.month}-{date.day}/{title}'

And this is not the only case where this was useful..
Maybe we can use our own DateTime implementation in FLOW3!?

Bastian Waidelich wrote:

Yes, but I'm unhappy about yet another syntax
[...]
Why hasn't the DateTime object more getters.. Then one could write

So, in the pattern one could use the object path syntax as in Fluid. Nice idea.

Maybe we can use our own DateTime implementation in FLOW3!?

Yeah, one more reason to have one...

Bastian Waidelich wrote:

As transliteration will most probably not make it into FLOW3 1.0, we'll have to find another (temporary) solution anyways.

Why not? The basics are all there, even in TYPO3 (v4).

Maybe we can make use of some built-in Doctrine functionality here (for example the sluggable behavior: http://www.doctrine-project.org/documentation/manual/1_0/en/behaviors:core-behaviors:sluggable -> https://github.com/l3pp4rd/DoctrineExtensions/tree/doctrine2.0.x/lib/Gedmo/Sluggable)

Oh, well, looks interesting, why not mix and match the best from our and their code. Either way, having this in I18n by 1.0 should be no problem. Even it's some kind of "workaround", I'd put it there. We should discuss your needs and just do it.

FYI: The current implementation supports following syntax:

-
  name: 'Single Post Actions'
  uriPattern:    'posts/{post}(/{@action})'
  defaults:
    '@package':    'TYPO3.Blog'
    '@controller': 'Post'
    '@action':     'show'
    '@format':     'html'
  routeParts:
    post:
      objectType: TYPO3\Blog\Domain\Model\Post

By default the @identity property/ies of the specified object type are used to create the URI section, or - if they're not specified - the technical identifier (UUID) of the respective object.
Alternatively a custom URI pattern can be specified:

-
  name: 'Single Post Actions'
  uriPattern:    'posts/{post}(/{@action})'
  defaults:
    '@package':    'TYPO3.Blog'
    '@controller': 'Post'
    '@action':     'show'
    '@format':     'html'
  routeParts:
    post:
      objectType: TYPO3\Blog\Domain\Model\Post
      uriPattern: '{date:Y}/{date:m}/{date:d}/{title}'

Patch set 2 of change I8fb5d4f4be3649e2f6307f83af2f3bbaa2191b5b has been pushed to the review server.
It is available at http://review.typo3.org/5076

Patch set 3 of change I8fb5d4f4be3649e2f6307f83af2f3bbaa2191b5b has been pushed to the review server.
It is available at http://review.typo3.org/5076

Patch set 4 of change I8fb5d4f4be3649e2f6307f83af2f3bbaa2191b5b has been pushed to the review server.
It is available at http://review.typo3.org/5076