Engine.GetSingleton() fails to resolve auto loaded nodes in C#

[mysticfall]

Godot version:
master / 0e6e98a

OS/device including version:
Manjaro Linux 17.1-rc2

Issue description:
If I have an auto loaded node named RootContext, running the following code fails to resolve the node instance with an error, "Failed to retrieve non-existent singleton 'RootContext'":

var context = Engine.GetSingleton("RootContext");

However, the following code correctly resolves and retrieves the node correctly in the same settings (invoked inside another Node instance):

var context = GetNode("/root/RootContext");

I'm not entirely sure if it's the correct way to resolve singletons in C# though.

[neikeq]

Does Engine.get_singleton("RootContext") work in GDScript. If I'm not wrong, it only returns internal singletons like Input, Engine, OS or ResourceLoader.
I could add a method to make that less annoying than the GetNode code.

[mysticfall]

Sorry, since there's no real documentation for C# binding yet, I had to guess what could be the equivalent of referencing autoloaded singletons by their names and seems I was wrong 😅 .

It'd be indeed nice to have such a method somewhere. Anyway, you can close this issue if GetSingleton isn't supposed to do what I thought it would.

[neikeq]

What has to be done about this? Engine.GetSingleton(name) only returns the engine singletons (Input, OS, ProjectSettings, Engine itself, etc).

As it can be seen in the documentation page GetNode("/root/RootContext") is indeed the correct way of accessing the node. However, GDScript has the syntax sugar of using an identifier for accessing it as an alternative to get_node.

[neikeq]

Perhaps something like a GetAutoLoad("RootContext") method in Node?

[mysticfall]

@neikeq Revisiting this issue, I'm amazed at how clueless I was about Godot back then 😅

But yeah, something like that would be good to have, because /root/RootContext is not that intuitive and you don't always have a node reference in your code.