Add typed return for Object.defineProperties

Search Terms

Object.defineProperties typed

Suggestion

const newObject = Object.defineProperties(o, map);

Use Cases

Creating extensions of certain properties while still being able to type-check them

Examples

/** @type {NodeList} */
const nodeListObject = Object.defineProperties(/** @type {Node[]} */ ([]), {
    item: {
      enumerable: false,
      /** @param {number} [index] */
      value: function item(index) { return this[index]; },
    },
  });

Checklist

My suggestion meets these guidelines:

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
• This feature would agree with the rest of TypeScript's Design Goals.

The current type I'm using is the following:

interface ObjectConstructor {
  defineProperties<T1, T2 = PropertyDescriptorMap>(o: T1, properties: T2 & ThisType<T1>): T1 & {
        [K in keyof T2]: (
          T2[K]['get'] extends Function ? ReturnType<T2[K]['get']> :
          T2[K]['set'] extends Function ? Parameters<T2[K]['set']>[0] :
          T2[K]['value'] extends undefined ? any : T2[K]['value']
        )
      };
}

It seems alright but I would love to get some feedback. Currently, I'm targeting against .get() first, then .set(arg0) and finally .value.

See: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/defineProperties

Inizia dal punto di ingresso Object.defineProperties e dalla firma ObjectConstructor proposta. Verifica come i casi get, set e value dovrebbero produrre un risultato tipizzato, usando la checklist di compatibilità e degli obiettivi di progettazione come vincoli; il lavoro è completato quando la tipizzazione del valore restituito richiesta è supportata senza modifiche a runtime.