zkoch commented on this pull request. > </p> + <ol class="algorithm"> + <li>Let <var>url</var> be the result of running the <a>URL parser</a> + on <var>input</var>. + </li> + <li>If failure, <a>throw</a> a <code>TypeError</code> exception. + </li> + <li>If running <a>potentially trustworthy URL</a> with <var>url</var> Query strings just feel more complicated to me and much easier for developers to get wrong. The whole goal was to give us the flexibility of URLs (to enable things like method manifests) but also make it as tightly scoped as possible to prevent developer error. There's a *lot* of discussion on this at #9 -- 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/webpayments-method-identifiers/pull/35#discussion_r113848660
Received on Friday, 28 April 2017 04:14:29 UTC