Skip to content
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

Versioning issue in Apigility #2

Open
weierophinney opened this issue Dec 31, 2019 · 1 comment
Open

Versioning issue in Apigility #2

weierophinney opened this issue Dec 31, 2019 · 1 comment

Comments

@weierophinney
Copy link
Contributor

Just encountered a issue in while using a apigility.
As i am new i am not sure this is issue or existing flow of application.
This is the current situation i Created 3 module in api.

  1. Status - containing ping API
  2. Customer - containing test API
  3. User - containing test API

Eariler http://test.api/ping was working fine
but when i updated user module to version 2 and set its default version to 2.

my ping api of Status module stopped working and returned 404
but when i hit http://test.api/v1/ping
It works fine.

while debugging i found it was due to
'zf-versioning' => array(
'uri' => array(
0 => 'user.rest.test',
),
'default_version' => 2, //<this
),
in module config.

as its default version is changed to 2 but my other api is on default version of 1.


Originally posted by @gouravkhanna at zfcampus/zf-versioning#7

@diego-sorribas
Copy link

Same issue with different API, always get the last defaut_version key of all module.config arrays.

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

No branches or pull requests

2 participants