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

Doc #107

Merged
merged 6 commits into from
Dec 22, 2013
Merged

Doc #107

merged 6 commits into from
Dec 22, 2013

Conversation

bakura10
Copy link
Member

Hi everyone,

I've spent the whole afternoon writing doc for ZfrRest, now that I feel the API is stabilizing. I'd love to have some feedback, especially if the API makes sense, as it is explained!

Once this is done, I'll be able to tag version 0.1.0 =) !!

ping @danizord @Ocramius @mac_nibblet

ZfrRest and Apigility philosophies are completely different. ZfrRest is Doctrine only, and focuses only on a very
small subset on your REST API: it provides routing, validation and hydration.

On the other hand, Apigility comes with a graphical user interface, versioning support, authorization, authentication
Copy link
Member

Choose a reason for hiding this comment

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

Uhh, I'd rather say that we don't enforce that :)

Copy link
Member Author

Choose a reason for hiding this comment

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

Well... I'd love to create all those things for ZfrRest too :(.

Copy link
Member

Choose a reason for hiding this comment

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

Yes, you are just being hard with words in this README ;)

Copy link
Contributor

Choose a reason for hiding this comment

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

Missing a comma at the end of this line

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 0376fc9 on doc into 175fa75 on master.

HAL, content negotiation... ZfrRest will never provide **all** those functionalities, so if you need them, just go
with Apigility.

The truth is that I actually don't really like Apigility's architecture, and it does not integrate *that* well with
Copy link
Member

Choose a reason for hiding this comment

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

I don't think README has space for opinions :\

Copy link
Member Author

Choose a reason for hiding this comment

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

You're right :).

@Ocramius
Copy link
Member

Awesome PR! Also: will remove my comments if they don't affect changes

@coveralls
Copy link

Coverage Status

Coverage remained the same when pulling 58a83e3 on doc into 175fa75 on master.

@bakura10 bakura10 merged commit 05764b5 into master Dec 22, 2013
@bakura10 bakura10 deleted the doc branch December 22, 2013 23:03
@@ -17,6 +15,21 @@ Install the module by typing (or add it to your `composer.json` file):
Then, add the keys "ZfrRest" to your modules list in `application.config.php` file, and copy-paste the file
`zfr_rest.global.php.dist` into your `autoload` folder (don't forget to remove the .dist extension at the end!).

## ZfrRest vs Apigility

[Apigility](http://www.apigility.org) is a Zend Framework 2 module that also aims to simplify the creation of REST
Copy link
Contributor

Choose a reason for hiding this comment

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

It is more than a single module. From http://apigility.org/:

Apigility is an API Builder

@danizord
Copy link
Contributor

@bakura10 It seems I gave my feedback too late :)

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

Successfully merging this pull request may close these issues.

None yet

4 participants