Skip to content
This repository was archived by the owner on Apr 14, 2022. It is now read-only.

Fallback to function when property's declaringType is unknown - #1416

Merged
Jake Bailey (jakebailey) merged 1 commit into
microsoft:masterfrom
jakebailey:fix-1335
Aug 7, 2019
Merged

Jake Bailey (jakebailey) merged 1 commit into
microsoft:masterfrom
jakebailey:fix-1335

Conversation

@jakebailey

@jakebailey Jake Bailey (jakebailey) commented Aug 7, 2019 •

Copy link
Copy Markdown
Member

Fixes #1335, for now.

This could stand to be improved by somehow allowing the declaring type to be null, but that is a more complicated fix, and just falling back to a function provides some usability and stops the NREs.

@jakebailey
Jake Bailey (jakebailey) merged commit 2cab4fd into microsoft:master Aug 7, 2019
@jakebailey
Jake Bailey (jakebailey) deleted the fix-1335 branch August 7, 2019 17:49
Jake Bailey (jakebailey) added a commit to jakebailey/python-language-server that referenced this pull request Nov 1, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

@property outside of class definition causes NRE

2 participants