We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I plan to implement two LSP features:
The terminology is specific to Steep. I don't know if the definition is common to projects other than Steep.
Based on the terminology, the Goto Definition feature would work as follows:
Goto Implementation would navigate to implementation, and it cannot go to declaration.
(We can extend the definition to Goto declaration in a straightforward way.)
new
.new
...
The text was updated successfully, but these errors were encountered:
Confirmed how it works for ... overloaded methods:
def
class Foo def to_s: (Integer) -> void | ... # Overload with Object#to_s end
The Foo.new.to_s cannot resolve to Object#to_s.
Foo.new.to_s
Object#to_s
This is not the best behavior, but I think it's reasonable to ship without fixing the problem.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
I plan to implement two LSP features:
Terminology
The terminology is specific to Steep. I don't know if the definition is common to projects other than Steep.
Based on the terminology, the Goto Definition feature would work as follows:
Goto Implementation would navigate to implementation, and it cannot go to declaration.
(We can extend the definition to Goto declaration in a straightforward way.)
Pull requests
new
method call doesn't work well Handling goto-definition of.new
method #375...
overloaded methodThe text was updated successfully, but these errors were encountered: