jongleberry
jongleberry
This isn't really the purpose of this module. but I think we should be able to do `.names()` or something to get all the cookie names.
Ha was gonna remove that in the next major
Current behavior is intended :( I wanted the next version to have `.sign()` and `.encrypt()` as separate methods
can you clarify?
what info are you looking for? 1.0.0 will only show `.req` and `.res`. not sure if you want to hide those either. or did you just want something less noisy?
Ya but `cookie` is private. Heh
no idea. some tests would help. i think i just read somewhere that you shouldn't send certain values as cookie values. i'm sure most browsers handle this case anyways
meh if we don't need to do it then we shouldn't. if we're sure node isn't retarded in this aspect, then we can close it
thinking of the implementation. - if decryption fails (i.e. tampered), should it throw an error or just return null? or make it an option? i'd prefer throwing and unsetting, but...
damn this shit is super convoluted now. i'm just going to rewrite this library ~_~