Chris Tsou
Chris Tsou
This will be tricky to implement, throughtout the process there is a naive approach of keep what it's really needed discard or flatten everything else. I wouldn't discard any contribution...
One approach would be to identify these cases and fallback to the original simplify case??? I 've been thinking this one for days now...
This needs to be applied pretty much in all the converter interactions, not just the xml and for attributes, I like the idea a lot!
Resolve conflicts between different routes with their own persistent params. Example: Administrator panel with it's route ``` php Router::connect('admin/{:library}/{:controller}/{:action}/{:id}', array('admin' => true, 'library' => 'core', 'controller' => 'dashboard', 'action' =>...
You are using destroy like this and it doesn't work? `$("#demo1").navgoco('destroy');`
Thank you for the contribution @cercide this is something I wanted to tackle at some point!!!
Intresting case @HiImJulien self referencing group, I am on it ```xml ```
Oh I remembered, I have come accross something similar. Since nested (inner) classes are referring back to the parent class it creates this infinite loop during processing. I added back...
I think we can close this one, let me know if it didn't work for you @HiImJulien