[jifty-devel] Template::Declare Import Bug
ruslan.zakirov at gmail.com
Wed Oct 7 22:42:00 EDT 2009
On Thu, Oct 8, 2009 at 1:56 AM, David E. Wheeler <david at kineticode.com> wrote:
> On Oct 6, 2009, at 12:22 PM, Jesse Vincent wrote:
>>> A backwards-compatible change would be to allow the template class
>>> name to be passed, as I specified. If no argument is passed, it could
>>> fall back on the current behavior, which is simply the last class
>>> which it was imported.
>>> I should look at how aliasing affects this, too…
>> *nod* That sounds reasonable
> Crap. I just realized that this won't work either, because you can
> import the same templates into the same class with a different prefix.
> package Wifty::UI;
> import_templates Wifty::Mixin under '/mixout';
> import_templates Wifty::Mixin under '/mixin';
> So even if I called `path_for('hello', 'Wifty::UI')`, what would it
David, I took a look at path_for while we were discussing TD. It's
just a function we specific use case and may be it should be hidden
unless there requirement in similar general functionality.
> jifty-devel mailing list
> jifty-devel at lists.jifty.org
Best regards, Ruslan.
More information about the jifty-devel