Do we attach a getter/setter to the object?

Open
#1 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Start by reading the issue discussion and Bug 1886820, which debate whether Error.captureStackTrace should attach a getter or avoid one. The work is not ready to implement: a decision on the API design and the expected stack-trace behavior must be established first.

Written by the indexing model from the issue text.

Description

It's simpler and more straightforward to not use a getter.

In principle with a getter you could defer the work of formatting a stack trace until it's finally consumed.

Bug 1886820 has some discussion around this. Particularly, Matthieu Hoffman has some opinions against getters

Dominant language
No language data
Stars
15
Forks
5
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tc39/proposal-error-capturestacktrace

All issues in tc39/proposal-error-capturestacktrace

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.