Fixed in #bleedingEdge: === Name: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.36 Author: SvenVanCaekenberghe Time: 14 May 2014, 4:15:16.757748 pm UUID: 82c55065-f76b-4d21-8679-46d608bc68fc Ancestors: Zinc-Resource-Meta-Core-SvenVanCaekenberghe.35, Zinc-Resource-Meta-Core-SvenVanCaekenberghe.34
Change ZnUrl>>#pathSegments to return an empty collection instead of nil (thx Sean DeNigris) Merge some ZnUrl 'query accessing' methods back in === Name: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.22 Author: SvenVanCaekenberghe Time: 14 May 2014, 4:15:58.85477 pm UUID: d2018df2-4fd0-440c-a0f7-358315e9a0fd Ancestors: Zinc-Resource-Meta-Tests-SvenVanCaekenberghe.21 Change ZnUrl>>#pathSegments to return an empty collection instead of nil (thx Sean DeNigris) === On 11 May 2014, at 15:04, Sean P. DeNigris <s...@clipperadams.com> wrote: > Sven Van Caekenberghe-2 wrote >> But I understand the confusion, I'll flag this for my todo/tothink > > - Conceptually, an empty collection seems to fit better e.g. there is: > self assert: 'http://google.com/' asUrl queryKeys isEmpty > - It also makes processing easier because you can just "url pathSegments do: > aBlock" without always having to do a check first. This is how I found the > problem - my code was working until I passed it a url with an empty path. > > > > ----- > Cheers, > Sean > -- > View this message in context: > http://forum.world.st/Possible-Zinc-Bug-empty-path-segments-returns-nil-tp4758371p4758666.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >
