Ticket Details

Bug in `Cookie::read()` with non-existent nested keys

BUG Ticket (closed) 

###What happened:
- something


###What was expected:
- something else
on 03.28.11 reported by: farhadi owned by: jperras

Updates

on 03.28.11 by farhadi 
###Test Case:
[http://dev.lithify.me/forks/farhadi/lithium/commits/view/2d8a37bbf7be6cfb3a84e6a8a56cf864e1797fe0](http://dev.lithify.me/forks/farhadi/lithium/commits/view/2d8a37bbf7be6cfb3a84e6a8a56cf864e1797fe0)


###Patch:
[http://dev.lithify.me/forks/farhadi/lithium/commits/view/a336750b024f8d5cbd82e5f300018c46925c26c1](http://dev.lithify.me/forks/farhadi/lithium/commits/view/a336750b024f8d5cbd82e5f300018c46925c26c1)
on 06.05.11 by farhadi 
I guess I should add some description for this ticket :)

When reading a non-existent nested cookie, if there were no cookie defined in the specified configuration, it returns null which is correct but when there is some cookies previously defined, reading a non-existent nested cookie will return those cookies rather than the expected null value.

I was going to write a test for it then I found two tests called `testReadDotSyntax` and `testReadNestedKey` in the cookie adapter test cases which are logically the same. So I removed `testReadNestedKey` and modified the other one to prove this bug. And then I wrote that patch to fix it.
on 06.05.11 by jperras 
Ah, now that makes sense. It was a bit confusing from just reading the patches ;-).

Looks good (as always), farhadi. Doing some tests on it & merging it in.
(fixed) on 06.06.11 by jperras
  • owner was changed to jperras
  • status was changed to closed
  • resolution was changed to fixed
Fixed in [f0f9379869741673e72d1b2026286de3d4a25984] and [d2b32bd3ead32f95a3594eb67afedf52b101d52a] in master. Thanks!