Hacktoberfest 2026:メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

Option to omit private methods from gem RBIs, with a per-gem opt-in

オープン
#2,740 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 4 日以内に返信

@efegokdemir がすでに取り組んでいます。

2026年10月14日 から。

  • #2743 @efegokdemir による — オープン

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
30/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
ruby
領域
tooling

調査の方向性

Start with the Methods listener that skips private methods during tapioca gem and with merge_with_exported_rbi, which the issue says must run after filtering. Read how typed_overrides is parsed from the config to model the new gem options. Done means private_methods: false omits private methods except for gems in private_methods_for, and gems that export their own RBIs keep their private markers after the merge.

索引モデルが issue の本文から書いたものです。

説明

Problem

tapioca gem emits every private method it finds. Application code only reaches a gem's private methods through implicit-receiver calls from subclasses, including modules, or DSLs like Rake::DSL, so for most gems these definitions add size and diff churn without affecting type checking.

In a large Rails app (501 gems in the bundle, RBIs generated for 395), 332 of the generated RBIs contain private methods. After stripping private methods from all of them, srb tc passes once private methods are restored for just 9 gems:

  • rake: Rake::DSL#task, #namespace, #desc, called at the top level of every .rake file
  • activerecord: default_scope, transaction_include_any_action?
  • tapioca: Tapioca::Dsl::Compiler#compile_method_parameters_to_rbi, #compile_method_return_type_to_rbi, .all_classes, used by custom DSL compilers
  • rbi: RBI::Visitor#visit_*, which RBI::RBSPrinter overrides with override sigs in the gem's own RBI
  • karafka: Karafka::Instrumentation::Vendors::Datadog::MetricsListener#consumer_tags and #namespaced_metric, overridden by a subclass in another gem
  • super_diff, shoulda-matchers, rubocop, and one internal gem: helpers called from subclasses

Potential reduction

Keeping private methods for those 9 gems and omitting them for the other 386:

Before After Change
Method definitions 198,737 177,402 -10.7%
RBI size, excluding comments 14.3 MB 13.3 MB -7.2%
RBI size, total 38.8 MB 37.0 MB -4.8%
RBI lines, total 1,082,949 1,020,568 -5.8%

Gem upgrades that only touch private methods would also stop producing RBI diffs.

Proposal

A gem option that turns private methods off, plus a list of gems that keep them, similar in shape to typed_overrides:

gem:
  private_methods: false
  private_methods_for:
    - rake
    - activerecord

Defaulting private_methods to true keeps today's output.

Implementation note

We prototyped this with a patch loaded from sorbet/tapioca/require.rb. The filtering has to run after merge_with_exported_rbi. When the Methods listener skips private methods instead, gems that export their own RBIs (pdf-reader, rbi, spoom, prism) declare many of those methods without a private marker, and the merge brings them back as public methods.

Happy to open a PR if this sounds reasonable.

主要言語
Ruby
スター
874
フォーク
167
平均マージ
5日 12時間
マージ済み PR(30日)
11

環境構築

  • Dockerfile・Docker Compose ファイルなし
  • プルリクエストのテンプレートあり
  • コントリビューションガイドなし

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

Shopify/tapioca のほかの issue

Shopify/tapioca の issue をすべて見る

似ている issue

Ruby の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。