`Object#hasOwnProperty` and `Object.hasOwn` are overly restrictive

[ehoogeveen-medweb]

In #4 it was suggested to improve the typing to this is this & Record<Key, unknown> but b864600 seems to have set it to something closer to this is {} instead. As a result, none of the properties can queried or assigned to. For example:

const protoObj = { protoProp: 'protoProp' };

const obj: Record<string, string> = Object.create(protoObj);
obj.ownProp = 'ownProp';

for (const key in obj) {
  if (!obj.hasOwnProperty(key)) continue;
  console.log(obj[key]);
}

gives error Element implicitly has an 'any' type because expression of type 'string' can't be used to index type '{}'. No index signature with a parameter of type 'string' was found on type '{}'. (with noImplicitAny enabled). The example is a bit contrived, but this kind of loop is very common in older code where prototypes can't be trusted.

Was the intent to implement something like the intersection suggested in #4? I modified Object.hasOwn locally as follows:

  hasOwn<Obj extends object, Key extends PropertyKey>(
    o: Obj,
    v: Key
  ): o is Obj & (string extends Key
    ? {}
    : number extends Key
    ? {}
    : symbol extends Key
    ? {}
    : Key extends PropertyKey
    ? { [k in Key]: unknown }
    : {})

[uhyo]

Thank you, this is fixed in v2.2.0.