Hàm get trong Javascript

Trong bài này chúng ta sẽ tìm hiểu hàm Array.find() trong Javascript, hàm find sẽ trả về giá trị của phần tử đầu tiên trong mảng thỏa mãn được điều kiện kiểm tra (được truyền vào như một hàm).

Hàm get trong Javascript

Hàm get trong Javascript

Bài viết này được đăng tại freetuts.net, không được copy dưới mọi hình thức.

Hàm find sẽ lần lượt sử dụng các phần tử của mảng để thực hiện hàm kiểm tra cho đến khi có giá trị thỏa mãn và hàm kiểm tra trả về true. Khi đó hàm find sẽ trả về giá trị của phần tử thỏa mãn và bỏ qua không kiểm tra các phần tử còn lại.

The

{
  get x() { }, get x() { }
}
0 syntax binds an object property to a function that will be called when that property is looked up.

Try it

Syntax

{ get prop() { /* … */ } }
{ get [expression]() { /* … */ } }

Parameters

{
  get x() { }, get x() { }
}
1

The name of the property to bind to the given function.

{
  get x() { }, get x() { }
}
2

You can also use expressions for a computed property name to bind to the given function.

Description

Sometimes it is desirable to allow access to a property that returns a dynamically computed value, or you may want to reflect the status of an internal variable without requiring the use of explicit method calls. In JavaScript, this can be accomplished with the use of a getter.

It is not possible to simultaneously have a getter bound to a property and have that property actually hold a value, although it is possible to use a getter and a setter in conjunction to create a type of pseudo-property.

Note the following when working with the

{
  get x() { }, get x() { }
}
0 syntax:

  • It can have an identifier which is either a number or a string;
  • It must have exactly zero parameters (see Incompatible ES5 change: literal getter and setter functions must now have exactly zero or one arguments for more information);
  • It must not appear in an object literal with another
    {
      get x() { }, get x() { }
    }
    
    0 e.g. the following is forbidden

    {
      get x() { }, get x() { }
    }
    

  • It must not appear with a data entry for the same property e.g. the following is forbidden

    {
      x: /* … */, get x() { /* … */ }
    }
    

Examples

Defining a getter on new objects in object initializers

This will create a pseudo-property

{
  get x() { }, get x() { }
}
5 for object
{
  get x() { }, get x() { }
}
6, which will return the last array item in
{
  get x() { }, get x() { }
}
7.

const obj = {
  log: ['example','test'],
  get latest() {
    if (this.log.length === 0) return undefined;
    return this.log[this.log.length - 1];
  }
}
console.log(obj.latest); // "test"

Note that attempting to assign a value to

{
  get x() { }, get x() { }
}
5 will not change it.

Deleting a getter using the { get x() { }, get x() { } } 9 operator

If you want to remove the getter, you can just

{
  get x() { }, get x() { }
}
9 it:

delete obj.latest;

Defining a getter on existing objects using { x: /* … */, get x() { /* … */ } } 1

To append a getter to an existing object later at any time, use

{
  x: /* … */, get x() { /* … */ }
}
2.

const o = {a: 0};

Object.defineProperty(o, 'b', { get() { return this.a + 1; } });

console.log(o.b) // Runs the getter, which yields a + 1 (which is 1)

Using a computed property name

const expr = 'foo';

const obj = {
  get [expr]() { return 'bar'; }
};

console.log(obj.foo); // "bar"

Defining static getters

class MyConstants {
  static get foo() {
    return 'foo';
  }
}

console.log(MyConstants.foo); // 'foo'
MyConstants.foo = 'bar';
console.log(MyConstants.foo); // 'foo', a static getter's value cannot be changed

Smart / self-overwriting / lazy getters

Getters give you a way to define a property of an object, but they do not calculate the property's value until it is accessed. A getter defers the cost of calculating the value until the value is needed. If it is never needed, you never pay the cost.

An additional optimization technique to lazify or delay the calculation of a property value and cache it for later access are smart (or memoized) getters. The value is calculated the first time the getter is called, and is then cached so subsequent accesses return the cached value without recalculating it. This is useful in the following situations:

  • If the calculation of a property value is expensive (takes much RAM or CPU time, spawns worker threads, retrieves remote file, etc.).
  • If the value isn't needed just now. It will be used later, or in some case it's not used at all.
  • If it's used, it will be accessed several times, and there is no need to re-calculate that value will never be changed or shouldn't be re-calculated.

Note: This means that you shouldn't write a lazy getter for a property whose value you expect to change, because if the getter is lazy then it will not recalculate the value.

Note that getters are not "lazy" or "memoized" by nature; you must implement this technique if you desire this behavior.

In the following example, the object has a getter as its own property. On getting the property, the property is removed from the object and re-added, but implicitly as a data property this time. Finally, the value gets returned.

const obj = {
  get notifier() {
    delete this.notifier;
    return this.notifier = document.getElementById('bookmarked-notification-anchor');
  },
}

get vs. defineProperty

While using the

{
  get x() { }, get x() { }
}
0 keyword and
{
  x: /* … */, get x() { /* … */ }
}
2 have similar results, there is a subtle difference between the two when used on
{
  x: /* … */, get x() { /* … */ }
}
5.

When using

{
  get x() { }, get x() { }
}
0 the property will be defined on the instance's prototype, while using
{
  x: /* … */, get x() { /* … */ }
}
2 the property will be defined on the instance it is applied to.