search

phly / PhlyRestfully

ZF2 module for creating RESTful JSON APIs using HAL and API-Problem
108 stars 45 forks source link

Allow the default controller class to be specified. #120

Closed elyobo closed 8 years ago

elyobo commented 10 years ago

Currently each resource can have a separate controller class specified, but there is no way to specify a default controller class to use where this is not specified; it's hard coded to PhlyRestfully\ResourceController.

This patch allows a global default controller class to be specified and defaults to PhlyRestfully\ResourceController if this is not specified.

elyobo commented 10 years ago

Hey, things have been pretty quiet around here lately. I just noticed this hadn't been merged when I shot myself in the foot by removing my local repo in composer.json and was wondering why everything broke subtly...

Any chance of getting this merged in?

ivan-novakov commented 10 years ago

I think that this project is obsolete. Check out the Apigility project, which (I think) has been inspired by PhlyRestfully:

https://www.apigility.org/

jaydiablo commented 10 years ago

This was used (but renamed) in Apigility.

New repo:

https://github.com/zfcampus/zf-rest

Rename commit:

https://github.com/zfcampus/zf-rest/commit/1268ce0e95ad0714698758a77e44916c075882dd

I assume this repo probably won't be updated much in the future. I don't know if one can just plugin ZFRest in place of PhlyRestfully though, we haven't attempted that yet with our project.

elyobo commented 10 years ago

OK, thanks for the suggestions. Both look interesting, but it looks like ZF rest is more likely to provide a smooth migration path.

jaydiablo commented 10 years ago

Yeah, Apigility is a full stack API builder complete with Admin interface, so may be overkill if you've already built code around Phlyrestfully. It does seem nice though, if it meets your project's requirements.