WebAssembly / WebAssembly/custom-descriptors
Be more precise about how properties are "installed"
Open
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 12
- Forks
- 3
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 1
Description
They should be "defined" rather than "set" so the existing prototype chains don't get involved. We should describe this in terms of Object.defineProperty and make sure methods are not enumerable.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Locate the property installation entry point and inspect how properties and methods are currently created. Compare the behavior with Object.defineProperty, including prototype-chain effects and method enumerability; done means the terminology describes properties as defined and methods are non-enumerable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, wasm
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100