Robin Ricard
Robin Ricard
Hi Jack, thanks for bringing up this proposal. It is a very interesting problem space to explore. The following comment is not an objection but something we might want to...
- **Affected package**: bs-graphql - **Type of issue**: FEATURE REQUEST ## Description Add a non-promise-based function call to the graphql query runner. See this conversation for more details: https://twitter.com/svensauleau/status/899175450429280256
### 💻 - [x] Would you like to work on this feature? ### What problem are you trying to solve? The polyfilled Records and Tuples are still objects so the...
- [x] [Spec text](https://tc39.es/proposal-record-tuple/) - [ ] Reviewers - [ ] @ljharb - [ ] @rkirsling - [ ] @brad4d - [ ] _You? Let `@rricard:mozilla.org` know on matrix if...
While writing spec text we found out that we could either allow writing new arbitrary props to the exotic record boxing object or simply disallow them. The champion group would...
Whenever we refer to "Record" inside of a spec document, we start referring to [6.2.1 The List and Record Specification Types](https://tc39.es/ecma262/#sec-list-and-record-specification-type) which is a spec-internal notion. This is going to...
Ensuring that no clashes exists between the web reality and this proposal is an essential precondition to Stage 3. This will require research work with implementers.
Hello, this draft PR is a prototype spec text that attempts to define a minimal interaction between the [Record & Tuple proposal for ECMAScript](https://github.com/tc39/proposal-record-tuple) and WebIDL. The proposal is currently...