-
Notifications
You must be signed in to change notification settings - Fork 2
.versionEye() method #103
Comments
@SherifWaly want to do this? It shouldn't be so complicated :D |
@amihaiemil Ok, I would like to do it :D |
@SherifWaly Right now, in the Organizations -> Teams -> Projects flow, 2 requests are passed: the one that is built along the way, and the original one (entry point, which is encapsulated by VersionEye). This is because, for instance, the Projects API starts the uri path from 0 again, instead of continuing it (it's not optimal, but it's how the API is designed). Now, instead of passing 2 requests, we will pass 1 request (the one which is built along the way) and the VersionEye instance:
Makes sense? And since Only do this change: replace that request with versionEye and write the If you have any other questions, ask away :) |
@amihaiemil Ok, thanks for explaining :) |
done, thanks :) |
A Team, a Project, an Organization etc should be able to return the original
VersionEye
instance, for convenience of usage.e.g.
RtVersioneye
should have a default-protected method to return the entry-point HTTP request.This way, instead of passing the entry request around, we just pass the original RtVersionEye.
The text was updated successfully, but these errors were encountered: