-
Notifications
You must be signed in to change notification settings - Fork 51
Global Apigility API URL prefix #51
Comments
This, as well as API-specific route prefixes, are something I would like to provide in future versions. We can likely handle them similarly to how we handle URI versioning (i.e., a listener that injects the prefix into configured routes). Marking as an enhancement request. |
Matthew, Remember this issues I’ve had with such configuration a couple of months ago. Changes would have to be made into the ZF2 router, besides injections through listeners. Julien. Le 15 juil. 2014 à 23:08, weierophinney [email protected] a écrit :
|
@weierophinney We need this feature in own project. I will be working on this on the next week, so I can create a merge request for this. I need only your advice where I should start |
@snapshotpl you've done something? some example? i need the same thing.. |
Yes. I will show something in next week.
|
perfect i'll wait for you 👍 |
@snapshotpl did you have any update? |
@stefanorg Tomorrow. |
@snapshotpl any news about this? i'm really interested in this feature |
any news on this feature? |
This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at laminas-api-tools/api-tools#67. |
I've been thinking it would be nice to have global setting to prefix all API's build using Apigility. This would make Apigility modules being more portable between projects - e.g. when you deploy Apigility server on it's own (e.g. APIs are available under api.example.com) or you use Apigility modules within another application (example.com/api).
This could be done by injecting Api related routes into general application router.
Currently we create routes under 'router'->'routes' config. My quick suggestion would be to move this into 'api-router'->'routes' or just 'api-routes' config array.
What do you think?
The text was updated successfully, but these errors were encountered: