Per last week's IRC meeting:

http://trac.symfony-project.org/wiki/IRCLogs20101202

...I implemented an extra parameter for route loader "type-hinting", useful
for cases where the resource string is ambiguous.  This is an alternative to
the "annotations:" prefix that was previously implemented.  Commit is here:

https://github.com/jmikola/symfony/commit/9fbea2adbf27710902c4dcd206ca86e98107192a

I originally spoke with Bulat about implementing this using DIC tags on the
loader services, but as I dug into the Routing\Loader namespace, I realized
this required more work than just dabbling in FrameworkBundle.  I'm not
crazy about the optional parameter I added to every supports(), resolve()
and load() method, but didn't think of an alternative.  If anyone has
suggestions/criticisms, please chime in.

Contrary to my original plans, I named the YAML/XML attribute "type" instead
of "loader", so a name change may be in order.  Personally, I think that
loader would be better suited to a string that uniquely identified a loader
service.  In our case, we want to hint that the format (or type) of the
resource is a certain name.  This is also open for debate.

I'd prefer to collect some feedback before opening a pull request for this,
as I'm sure there's work still to be done (more unit tests at least :)

-- 
jeremy mikola

-- 
If you want to report a vulnerability issue on symfony, please send it to 
security at symfony-project.com

You received this message because you are subscribed to the Google
Groups "symfony developers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/symfony-devs?hl=en

Reply via email to