Skip to content
New issue

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

Handle global classes when resolving type from PropertyInfo #85215

Merged

Conversation

HolonProduction
Copy link
Member

@HolonProduction HolonProduction commented Nov 22, 2023

Fixes partially #74888
Fixes partially #71296
Fixes partially #78454

Fixes partially #77643

Fixes partially godotengine/godot-proposals#8545 (Should be closed if #85239 is merged)

In theory we could also resolve to CLASS type if the file is GDScript but we would need to pass the completion context through the whole type resolve chain to add the depending parser. Not quite sure if this is worth the trouble.

Edit:
Sorting doesn't work since _get_property_location doesn't handle global classes. But I am a fan of smaller self contained PR's.

@HolonProduction
Copy link
Member Author

Just noticed we have the same behavior in the Analyzer. Should probably be changed there as well.

Copy link
Member

@vnen vnen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Do you want to make the change to the analyzer as well?

@HolonProduction HolonProduction force-pushed the type-from-property-class-name branch from c9dba82 to 4ab985d Compare January 17, 2024 20:40
@HolonProduction
Copy link
Member Author

Did the analyzer change as well

@akien-mga akien-mga merged commit b5dcb5f into godotengine:master Jan 18, 2024
15 checks passed
@akien-mga
Copy link
Member

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants