Ability to clone a `Hookable` instance / expose hooks list
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- TypeScript
- Stars
- 960
- Forks
- 43
- Avg merge
- 19m
- Merged PRs (30d)
- 1
Description
Describe the feature
I have a hooksA hookable with 10 hooks, I want to make an extended version of it with more hooks but does not mutate the original hooksA.
Additional information
- Would you be willing to help implement this feature?
Contributor guide
No contributing guide indexed for this repository
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
Start by locating the Hookable implementation and its existing tests; no file or entry point is named in the issue. Clarify whether the intended API is cloning an instance, exposing its hooks list, or both. Done means an extended hookable can gain hooks without mutating the original, with tests covering that behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100