- From: Domenic Denicola <notifications@github.com>
- Date: Wed, 03 Dec 2014 17:13:47 -0800
- To: webspecs/url <url@noreply.github.com>
Received on Thursday, 4 December 2014 01:14:13 UTC
> Different paths will indeed return different results. For some paths, the values of some of these values will remain undefined. It seems good to explicitly specify this somehow, so that the return type is consistent and matches the one in the header. So either explicitly set/return undefineds (or is it empty string? unclear) where necessary, or have some kind of rule in the prelude saying "if a field appears in the return statement but the steps don't specify its value, it is undefined/empty string." --- Reply to this email directly or view it on GitHub: https://github.com/webspecs/url/issues/5#issuecomment-65522255
Received on Thursday, 4 December 2014 01:14:13 UTC