Make Node.get_node() pause editor execution if it can't find the node

[ShalokShalom]

Describe the project you are working on:

Applies to all projects, GDScript.

Describe the problem or limitation you are having in your project:

Get_node can get the current node on an empty NodePath
Lots of bugs and confusion behavior occurs because of that.

Describe the feature/enhancement and how it helps to overcome the problem or limitation:

Yield an error, instead of accepting confusing behavior

Describe how your proposal will work, with code, pseudocode, mockups, and/or diagrams:

Already implemented: https://monnef.gitlab.io/golden-gadget

If this enhancement will not be used often, can it be worked around with a few lines of script?:

No

Is there a reason why this should be core and not an add-on in the asset library?:

This is similar to the nil issue and solved in some way that is always beneficial and never technically disadvantageous.

[Calinou]

I think we should just make get_node() pause the editor execution if the node can't be found (like GDScript errors do), but this isn't currently feasible.
Edit: It's feasible, see godotengine/godot#50955.

If you're not sure whether the node exists, use get_node_or_null() instead which fails silently if it can't find the node.

[Calinou]

When reading this proposal a second time, I realized it's about something different entirely. According to OP, get_node("") or $"" returns the current node, but I think it should result in an error similar to using a nonexistent node path. If you want to get the current node for some reason, you should use get_node(".") or $"." instead.

Either way, this should be addressed in a different pull request.

[ShalokShalom]

So I close this?

[Calinou]

@ShalokShalom I'll keep it open, as I think this proposal is still relevant.