Okay. There's a difference between exposing the state and requiring a developer to use the state. A design that _requires_ code that depends on the state value is one thing (and perhaps/probably would be a poorer design). But it doesn't follow that exposing the state does require depending on it. As I said, we've discussed this and I don't have a strong feeling about including it or not - in similar APIs we've found this type of attribute to be useful for debugging though that might not be the case here. --- Reply to this email directly or view it on GitHub: https://github.com/w3c/webpayments/issues/64#issuecomment-180023614Received on Thursday, 4 February 2016 20:00:32 UTC
This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:43:14 UTC