-
-
Notifications
You must be signed in to change notification settings - Fork 230
added Nette\Bridges #1446
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
added Nette\Bridges #1446
Conversation
|
UIMacros will be splitted into BlockMacros (in Latte) and UIMacros (in Bridges). |
|
I would keep current namespace of Nette DI extensions and only replaced references to various bridges. Since DI is not actual bridge but configuration of various settings (including databases) and I expect that Tracy will still be fundamental requirement for Nette at least couple of months. About separation to modules/libraries generally IMO I am not sure about name Bridges but nothing sounds to me way better (Adapters, Connectors). For mine style of separation Adapters would be more fitting name. |
|
O vote for Nette\Bridges\DI\Extension.php |
|
Well, the best way is to maintain only own namespaces a do not make options to use them when the other classes will be in the different repositories. So, the best should be
|
|
@hrach sry, I do not understand |
|
CS version:
|
|
Is bad idea move all bridges out of Nette directory? |
|
Oh shit… vypadlo mi |
|
@milo I think it should follow psr-0 |
|
@dg OK |
…ed to Bridges (BC break!)
All DI extensions, Tracy panels and Latte macros moved to Nette\Briges.
In fact, I am not sure this directory structure is OK. Should it be
Nette\Bridges\DI\NetteExtension.phpNette\Bridges\DI\Nette\Extension.phporNette\Bridges\Nette\DI\Extension.php?