-
Notifications
You must be signed in to change notification settings - Fork 12
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
The expediency of using the MvcEvent #44
Comments
hi @popovserhii from my site, i never used the zf-expressive way, so i know just some basics about it. But we have to start to think about the dependencies, at the begin, what we can remove and optimize. if you want you can join https://gitter.im/zfc-datagrid/Lobby maybe we can think together about it. |
Hi @kokspflanze @popovserhii |
Hi @imonteiro "require": {
"zfc-datagrid/zfc-datagrid": "dev-expressive"
},
"repositories": [
{
"type": "vcs",
"url": "https://github.com/popovserhii/zfc-datagrid"
}
] add We can cooperate and implement support of ZF Expressive, but @kokspflanze should tell how to organize the process. |
hi @popovserhii atm i work on next version, i dont have a problem if the module can support both, expressive and mvc, is that possible, or to much differences? |
@kokspflanze, there is only one thing, we should discard from MvcEvent and use Request object instead. I can do PR in |
@popovserhii okay, sure you can open a PR with that =), so big goal for 2.0 will be the Expressive support. |
I've wanted to adapt your module to ZF Expressive but see that code is using MvcEvent.
Expressive application doesn't have any registered "application" class and that to cause the problem.
I've gone through the code and see that there isn't real usage of MvcEvent. This only need to getting Request object.
Can we reduce using of MvcEvent and simply inject Request object?
The text was updated successfully, but these errors were encountered: