Handle visibility properly for abstract methods

Open
#6 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
tooling

Research direction

Start with the implementation introduced in issue #2 and trace how abstract methods answer respond_to_missing?. Check the include_private argument for both visibility cases, then add or update coverage so private methods are distinguished from public methods and the behavior matches Ruby's respond_to? contract.

Written by the indexing model from the issue text.

Description

The initial implementation in #2 completely ignores the include_private parameter of respond_to_missing?

Dominant language
Ruby
Stars
3
Forks
5
Avg merge
8d 23h
Merged PRs (30d)
8

Contributor guide

No contributing guide indexed for this repository

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 Shopify/type_toolkit

All issues in Shopify/type_toolkit

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.