Skip to content

restore sorbet check for dead code#396

Merged
yob merged 1 commit intomainfrom
check-dead-code-again
Nov 21, 2021
Merged

restore sorbet check for dead code#396
yob merged 1 commit intomainfrom
check-dead-code-again

Conversation

@yob
Copy link
Copy Markdown
Owner

@yob yob commented Nov 21, 2021

Originally disabled in PR #395, but I got some advice on how to re-enable it on stackoverflow.

I'm not sure I even want this kind of check really, given how inconsistently they're used across the codebase. Maybe they have value, but only on the public API? Anyway, for now I'm focused on defining types in Sorbet rather than changing behaviour.

Originally disabled in PR #395, but I got some advice on how to re-enable
it at [1].

I'm not sure I even want this kind of check really, given how
inconsistently they're used across the codebase. Maybe they have value,
but only on the public API? Anyway, for now I'm focused on defining
types in Sorbet rather than changing behaviour.

[1] https://stackoverflow.com/questions/70051079/how-should-i-manage-sorbet-errors-in-a-gem-where-type-info-must-be-in-rbi-files
@yob yob force-pushed the check-dead-code-again branch from 7032b54 to 6608364 Compare November 21, 2021 05:23
@yob yob merged commit 175c443 into main Nov 21, 2021
@yob yob deleted the check-dead-code-again branch November 21, 2021 05:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant