- From: Mounir Lamouri <notifications@github.com>
- Date: Mon, 31 Oct 2016 04:00:03 -0700
- To: w3c/manifest <manifest@noreply.github.com>
Received on Monday, 31 October 2016 11:00:43 UTC
Maybe that was on purpose (no pun intended) but it sounds fairly odd that `purpose` parsing will return `undefined` when the value isn't a string but a set with `"any"` if the value is a string but doesn't contain a known value. I would suggest to do something similar to `icons` where the same value (empty array) is returned regardless of the type of errors. Here, we could return an empty set. (As a side note, is space separated keywords more common in JSON than comma separated? HTML uses comma separated most of the time, doesn't it?) CC @marcoscaceres -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/513
Received on Monday, 31 October 2016 11:00:43 UTC