- From: jan-ivar via GitHub <sysbot+gh@w3.org>
- Date: Fri, 25 Aug 2017 14:27:11 +0000
- To: public-webrtc-logs@w3.org
This is a good example of why we can't use `required` *solely* to guarantee what's being returned, because the same dictionary is also the input to `setParameters` where its primary normative meaning causes `TypeErrors` in that method if members are missing. At the same time, it may be a good example of where the two requirements align, allowing us to do just that. In general, this may be a good measuring stick: for any get method returning a dictionary, imagine a future set method taking that argument, if one does not currently exist, and use that to guide what should be `required`. If that ends up matching what we want, great! It seems to me we could at least make [transactionId](http://w3c.github.io/webrtc-pc/#dom-rtcrtpparameters-transactionid) `required`, based on its stated intent. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1493#issuecomment-324936228 using your GitHub account
Received on Friday, 25 August 2017 14:27:08 UTC