You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Imagine this situation:
We have typical multiplayers with signals scene.
Every time you need to call RPC you type something like this: Rpc(nameof(NameOfMethod), SomeFormOfArg1, SomeFormOfArg2);
Or for example you need to emit signal, you use this construction: EmitSignal(nameof(OnSignalHappened), SomeFormOfArg1, SomeFormOfArg2);
Or for example you need to connect to signal: Connect(nameof(OnSignalHappened), this, nameof(SomeMethodThatHasArgs));
Aswell as disconnect: Disconnect(nameof(OnSignalHappened), this, nameof(SomeMethodThatHasArgs));
Rider does understand that first is string and other objects is param of objects (for passing args), but rider also doesn't understand that it's indirectly related to methods and it's args.
What would be nice is to have additional check for such stuff.
For example, if we write one of those methods above with less than required methods, or with more, or with wrong type, it would highlight it as error about wrong type or amount of args.
As far as i know, there's not much of work being done for full support on c# side even in 4.0, i've seen only signals as events, so it's unlikely that this typing would be changed soon.
The text was updated successfully, but these errors were encountered:
Imagine this situation:
We have typical multiplayers with signals scene.
Every time you need to call RPC you type something like this:
Rpc(nameof(NameOfMethod), SomeFormOfArg1, SomeFormOfArg2);
Or for example you need to emit signal, you use this construction:
EmitSignal(nameof(OnSignalHappened), SomeFormOfArg1, SomeFormOfArg2);
Or for example you need to connect to signal:
Connect(nameof(OnSignalHappened), this, nameof(SomeMethodThatHasArgs));
Aswell as disconnect:
Disconnect(nameof(OnSignalHappened), this, nameof(SomeMethodThatHasArgs));
Rider does understand that first is string and other objects is param of objects (for passing args), but rider also doesn't understand that it's indirectly related to methods and it's args.
What would be nice is to have additional check for such stuff.
For example, if we write one of those methods above with less than required methods, or with more, or with wrong type, it would highlight it as error about wrong type or amount of args.
As far as i know, there's not much of work being done for full support on c# side even in 4.0, i've seen only signals as events, so it's unlikely that this typing would be changed soon.
The text was updated successfully, but these errors were encountered: