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

Why req is not available in read calls? #11

Closed
fatganz opened this issue Aug 27, 2014 · 3 comments
Closed

Why req is not available in read calls? #11

fatganz opened this issue Aug 27, 2014 · 3 comments

Comments

@fatganz
Copy link

fatganz commented Aug 27, 2014

Is there a reason why req param is omitted in request for read operations in middleware?
Or is there another way i can have req available for read using middleware?

@fatganz fatganz closed this as completed Aug 27, 2014
@fatganz fatganz reopened this Aug 27, 2014
@Vijar
Copy link
Contributor

Vijar commented Aug 27, 2014

The middleware passes the req object to the Fetcher.single function:

req: req,

Fetcher.single function passes this req object on to all CRUD fetcher access functions:

req = request.req,

Is there something else I'm not noticing?

@fatganz
Copy link
Author

fatganz commented Aug 27, 2014

But in case of GET (read, req isn't passed)

request = {

At least i can't access it there.
p.s. Thanks for your reply!

@Vijar
Copy link
Contributor

Vijar commented Aug 27, 2014

Ohh you're right, will fix.

@Vijar Vijar closed this as completed in c641d7e Aug 27, 2014
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

No branches or pull requests

2 participants