Using Respect?

[augustohp]

@jeanpimentel What are your thoughts on using some Respect components?

With Rest instead of Silex for example, we could use the same controller/route as an HTML and a REST (api) route. This could be useful for us in many ways...

But I (and I belive @alganet too) don't really want to put something that sits in the way between you and the code. I think it is important for all of us to feel confortable with the code, I am confortable with the used components since I already used them for some things... =D

[jeanpimentel]

I used Silex just for convenience, and I have nothing against change it to Rest. My focus when I started was more in the GitHub API and since the project is at beginning, we can change it now.

[augustohp]

Great, You can still code the classes you need with the standard PSR-0 autoloader, it will work just fine. ;D I have not much time now, but expect something this weekend similar to repository Resplendor from @alganet

[diegoholiveira]

I agree with this change but, can we do this change applying tests? We can also use just the sf2 components that we really use instead of use all whole project.

Let's create a roadmap do this migration.

[alganet]

Silex is already working, if we stick to the microframework style we should keep it. A possible advantage of Respect\Rest over Silex is the possibility to use class Controllers, but I don't know how this could help us now. It isn't hard to move from one to another anyway.

As @diegoholiveira noted, testing is critical. We could write functional tests that hit the controllers, then if one day we decide to move our tests will telll us of any failure to comply with our own API.

[augustohp]

I just put Respect on the scene because i haven't run the composer install =D