memcached came from nowhere #1
Comments
|
Very true. It shouldn't be a requirement for using the library, but it's much easier to demonstrate retrieving session data from an accessible store rather than process memory. If you're having specific difficulties, it would be great to get a little more detail for a diagnosis and fix. Otherwise I'd love to merge some, ah, clarification around the readme! |
|
I am confused about the "Accessing session data" as well. Would be nice to have a more detailed tutorial ! |
Supertest-session's cookie jar exposes session cookies for inspection or reuse in downstream tests. The library makes no presumptions about what those tests might entail, however, so it's rather confusing to bring in a specific session store.
|
Thanks for the nudge, @wonay! As session storage is outside the scope of this library, I think it may be best to simply drop that note from the README (See #25). The goal of the (rather confusing) original example was to show how to access cookies from supertest-session's cookie jar for reuse against a backend session store. But it seems enough to show how to get at them, and leave it up to individual applications to decide if (and how) take to it from there. That said, store-specific tutorials sound like a fantastic idea! If anyone is working with a specific store and would be willing to link up (or PR a link to) an example, it might save others some setup time (and confusion). |
No description provided.
The text was updated successfully, but these errors were encountered: