Make `Tracer.trace` support an optional second argument for ivar
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Ruby
- Stars
- 95
- Forks
- 8
- PR merge metrics
- No merged PRs in 30d
Description
In #16 IvarTracer was added, which also targets a specific object. So instead of introducing another Tracer method for it, perhaps we can extend Tracer.trace instead:
Tracer.trace(obj) # => uses ObjectTracer
Tracer.trace(obj, :@ivar) # => uses IvarTracer
(This idea was provided by @KaanOzkan)
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 reading the existing Tracer.trace entry point and the ObjectTracer and IvarTracer implementations referenced in the issue. Check how current tracing behavior is tested, then verify that Tracer.trace(obj) retains ObjectTracer behavior and Tracer.trace(obj, :@ivar) selects IvarTracer for the requested instance variable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100