A hint

[Runrioter]

This repo is based on pillarjs/cookies.
And It extends with an encrypt/decrypt function that can't be customized.
I think that pure cookie getter and setter are fine.

• if cookie is used for fetching session, this approach (feat: make encode/decode support store-based session koajs/session#100) is ok.
• Or, any customized separate encrypt/decrypt function is used smoothly. It is not necessary to have a new options.

What do u think?

: ) Looking forward this PR((koajs/session#100) is merged

[atian25]

sorry, don't notify this, you should open issue at https://github.com/eggjs/egg/issues

cc @dead-horse