Skip to content
This repository has been archived by the owner on Jan 21, 2020. It is now read-only.

Global Apigility API URL prefix #51

Open
matuszeman opened this issue Jun 18, 2014 · 11 comments
Open

Global Apigility API URL prefix #51

matuszeman opened this issue Jun 18, 2014 · 11 comments

Comments

@matuszeman
Copy link

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?

@weierophinney
Copy link
Member

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.

@jguittard
Copy link

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.
But the need is effective.

Julien.

Le 15 juil. 2014 à 23:08, weierophinney [email protected] a écrit :

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.


Reply to this email directly or view it on GitHub.

@snapshotpl
Copy link
Contributor

@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

@stefanorg
Copy link

@snapshotpl you've done something? some example? i need the same thing..

@snapshotpl
Copy link
Contributor

Yes. I will show something in next week.
3 sty 2015 16:35 "stefanorg" [email protected] napisał(a):

@snapshotpl https://github.com/snapshotpl you've done something? some
example? i need the same thing..


Reply to this email directly or view it on GitHub
#51 (comment)
.

@stefanorg
Copy link

perfect i'll wait for you 👍

@stefanorg
Copy link

@snapshotpl did you have any update?

@snapshotpl
Copy link
Contributor

@stefanorg Tomorrow.
@weierophinney when you plan to release 1.1?

@ildanno
Copy link

ildanno commented Apr 23, 2015

@snapshotpl any news about this? i'm really interested in this feature

@remizyaka
Copy link

any news on this feature?

@michalbundyra
Copy link
Member

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.

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

No branches or pull requests

8 participants