Skip to content

Namespace change #11

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

Merged
merged 5 commits into from
Dec 7, 2017
Merged

Namespace change #11

merged 5 commits into from
Dec 7, 2017

Conversation

icanhazstring
Copy link
Member

Changelog

  • move namespace according to goaop namespace.
  • add functional test for warmup
  • remove zf2 specific namings

Version suggestion: 2.0

Question:
I don't quite know if it works with ZF3 as a module. Do we need the support here or should we simply point to the new zend-expressive-middleware for goaop? Otherwise I would add a comment in the README.md to point that one out and remove the requirement in composer.json

composer.json Outdated
@@ -6,7 +6,8 @@
"license": "MIT",
"require": {
"goaop/framework": "^1.0|^2.0",
"zendframework/zend-modulemanager": "^2.0 | ^3.0"
"zendframework/zend-modulemanager": "^2.0 | ^3.0",
"symfony/console": "^3.0 || ^4.0"
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What about the idea to put this just in the suggests section because it is not needed to use this module. It is just needed if you want to run the warm up command?

Copy link
Member Author

@icanhazstring icanhazstring Dec 1, 2017

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good point. Will change that and revoke the change in the binary to check if it is installed

@reinfi
Copy link
Contributor

reinfi commented Dec 1, 2017

Good work.

It works with ZF3. We could adjust the tests to let them run with ZF2 and ZF3. I could do this when this PR is merged.

And Version 2.0 sounds good.

@icanhazstring
Copy link
Member Author

@reinfi could u check the warmup script as well then? If that works we could maybe change the naming too and remove zf2 from it

Change namespace according to new specification.
\Go\Zend\Framework
This will remove zf2 specific namings. These would mitmatch zend framework
if you want to use this with ZF3.

This will also add another functional test for goaop-warmup.
Also add requirement for symfony/console since this is needed for warmup.
This is needed to actually run the functional warmup test
Copy link
Contributor

@reinfi reinfi left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me it is fine, I think @lisachenko should have a look at it if he is fine with the new namespace. And then we are good to go for version 2.0 :-)

@icanhazstring
Copy link
Member Author

icanhazstring commented Dec 5, 2017

Yep. Maybe we should then split up master as 1.x to support some kind of backwards patches and then merge this.

@lisachenko
Copy link
Member

Hi, for me this PR is ok! Just bump master to the next major version to keep BC promise and push current master branch as 1.x

@lisachenko
Copy link
Member

PS. Regarding cache warming process: there is the CacheWarmer service in the framework itself, thanks to @TheCelavi. This service can be reused in bridges or by extending CacheWarmupCommand like in SF2 https://github.com/goaop/goaop-symfony-bundle/blob/master/Command/CacheWarmupCommand.php.

@icanhazstring
Copy link
Member Author

Good point tho. I'll create an enhancement ticket for us to rework the warmup then

@icanhazstring icanhazstring merged commit 615cfa0 into goaop:master Dec 7, 2017
@icanhazstring
Copy link
Member Author

Ticket Created: #13
Branch master to 1.x for BC
Bumped version to 2.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants