Skip to content

Conversation

@tk0miya
Copy link
Contributor

@tk0miya tk0miya commented Oct 18, 2024

Steep is a type checker for Ruby.

The new option; AllowSteepAnnotation for Layout/LeadingCommentSpace allows to use Steep's annotation comments in the Ruby code.

refs: https://github.com/soutaro/steep/wiki/Release-Note-1.3#add-type-assertion-and-type-application-syntax

Replace this text with a summary of the changes in your PR.
The more detailed you are, the better.


Before submitting the PR make sure the following are checked:

  • The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
  • Wrote good commit messages.
  • Commit message starts with [Fix #issue-number] (if the related issue exists).
  • Feature branch is up-to-date with master (if not - rebase it).
  • Squashed related commits together.
  • Added tests.
  • Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
  • Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

[Steep](https://github.com/soutaro/steep) is a type checker for Ruby.

The new option; `AllowSteepAnnotation` for `Layout/LeadingCommentSpace`
allows to use Steep's annotation comments in the Ruby code.

refs: https://github.com/soutaro/steep/wiki/Release-Note-1.3#add-type-assertion-and-type-application-syntax
@tk0miya tk0miya force-pushed the leading_comment_space/allow_steep_annotation branch from 3ce9a53 to d1835ed Compare October 18, 2024 16:25
@bbatsov bbatsov merged commit 7e82e44 into rubocop:master Oct 18, 2024
@tk0miya tk0miya deleted the leading_comment_space/allow_steep_annotation branch October 19, 2024 02:54
@tk0miya
Copy link
Contributor Author

tk0miya commented Oct 19, 2024

Thanks!

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.

2 participants