Open snatvb opened 2 weeks ago
https://github.com/godotengine/godot/issues/93366 Created on Godot, if there is no point in improving the macro, you can close it down
godotengine/godot#93366 Created on Godot, if there is no point in improving the macro, you can close it down
i dont see why this issue should be brought up to godot
i dont see why this issue should be brought up to godot
Bromeon said that it's issue of Godot that it doesn't notify about incorrect export property
Sorry about the confusion here, tried to clarify it on the Godot issue.
I'm not sure whether Godot performs the same validations for @export_*
annotations in GDScript as it does for GDExtension property hints. If it doesn't (and there is no change planned), then we would need to replicate them on Rust side, which could be quite laborious and maintenance-intensive.
If user tries convert
@export_file("*.txt")
to Array:LSP shows error:
And in console:
![image](https://github.com/godot-rust/gdext/assets/1572963/5646095d-a992-49d2-ab98-738840f9773b)
But if user does it in rust:
It leads to this:
![image](https://github.com/godot-rust/gdext/assets/1572963/2db4c31a-6431-4b46-afbf-09945905f3cd)
For user it's unexpected and it would be rather to notify about incorrect annotation.
Reprocase: godot-rust-repro.zip
Discord source conversation