Object.getOwnPropertyNames()

最新推荐文章于 2021-04-28 17:20:31 发布

hao5743

最新推荐文章于 2021-04-28 17:20:31 发布

阅读量1.6k

点赞数

分类专栏： JavaScript 编程

本文链接：https://blog.csdn.net/hao5743/article/details/51658278

版权

编程同时被 2 个专栏收录

65 篇文章 0 订阅

订阅专栏

JavaScript

42 篇文章 0 订阅

订阅专栏

The Object.getOwnPropertyNames() method returns an array of all properties (enumerable or not) found directly upon a given object.

Syntax

Object.getOwnPropertyNames(obj)

Parameters

obj

The object whose enumerable and non-enumerable own properties are to be returned.

Description

Object.getOwnPropertyNames() returns an array whose elements are strings corresponding to the enumerable and non-enumerable properties found directly upon obj. The ordering of the enumerable properties in the array is consistent with the ordering exposed by a for...in loop (or byObject.keys()) over the properties of the object. The ordering of the non-enumerable properties in the array, and among the enumerable properties, is not defined.

Examples

Using `Object.getOwnPropertyNames()`

var arr = ['a', 'b', 'c'];
console.log(Object.getOwnPropertyNames(arr).sort()); 
// logs ["0", "1", "2", "length"]

// Array-like object
var obj = { 0: 'a', 1: 'b', 2: 'c' };
console.log(Object.getOwnPropertyNames(obj).sort()); 
// logs ["0", "1", "2"]

// Logging property names and values using Array.forEach
Object.getOwnPropertyNames(obj).forEach(function(val, idx, array) {
  console.log(val + ' -> ' + obj[val]);
});
// logs
// 0 -> a
// 1 -> b
// 2 -> c

// non-enumerable property
var my_obj = Object.create({}, {
  getFoo: {
    value: function() { return this.foo; },
    enumerable: false
  }
});
my_obj.foo = 1;

console.log(Object.getOwnPropertyNames(my_obj).sort()); 
// logs ["foo", "getFoo"]

If you want only the enumerable properties, see Object.keys() or use a for...in loop (although note that this will return enumerable properties not found directly upon that object but also along the prototype chain for the object unless the latter is filtered with hasOwnProperty()).

Items on the prototype chain are not listed:

function ParentClass() {}
ParentClass.prototype.inheritedMethod = function() {};

function ChildClass() {
  this.prop = 5;
  this.method = function() {};
}
ChildClass.prototype = new ParentClass;
ChildClass.prototype.prototypeMethod = function() {};

console.log(
  Object.getOwnPropertyNames(
    new ChildClass() // ["prop", "method"]
  )
);

Get Non-Enumerable Only

This uses the Array.prototype.filter() function to remove the enumerable keys (obtained withObject.keys()) from a list of all keys (obtained with Object.getOwnPropertyNames()) leaving only the non-enumerable keys.

var target = myObject;
var enum_and_nonenum = Object.getOwnPropertyNames(target);
var enum_only = Object.keys(target);
var nonenum_only = enum_and_nonenum.filter(function(key) {
  var indexInEnum = enum_only.indexOf(key);
  if (indexInEnum == -1) {
    // not found in enum_only keys mean the key is non-enumerable,
    // so return true so we keep this in the filter
    return true;
  } else {
    return false;
  }
});

console.log(nonenum_only);

Notes

In ES5, if the argument to this method is not an object (a primitive), then it will cause a TypeError. In ES6, a non-object argument will be coerced to an object.

Object.getOwnPropertyNames('foo');
// TypeError: "foo" is not an object (ES5 code)

Object.getOwnPropertyNames('foo');
// ["0", "1", "2", "length"]  (ES6 code)

Specifications

Specification	Status	Comment
ECMAScript 5.1 (ECMA-262) The definition of 'Object.getOwnPropertyNames' in that specification.	Standard	Initial definition. Implemented in JavaScript 1.8.5.
ECMAScript 2015 (6th Edition, ECMA-262) The definition of 'Object.getOwnPropertyNames' in that specification.	Standard
ECMAScript 2017 Draft (ECMA-262) The definition of 'Object.getOwnPropertyNames' in that specification.	Draft

Feature	Chrome	Firefox (Gecko)	Internet Explorer	Opera	Safari
Basic support	5	4.0 (2)	9	12	5

SpiderMonkey-specific notes

Prior to SpiderMonkey 28 (Firefox 28 / Thunderbird 28 / SeaMonkey 2.25 / Firefox OS 1.3),Object.getOwnPropertyNames did not see unresolved properties of Error objects. This has been fixed in later versions (bug 724768).