Fix bug where CommandSender would not reenable after being disabled

[jamiebrynes7]

Description

If you have a behaviour that looks like:

public class MyBehaviour : MonoBehaviour 
{
	[Require] private ComponentCommandSender sender;
	[Require] private OtherComponentCommandReceiver receiver;
}

If this behaviour is disabled due to OtherComponent losing authority, receiver will be set to null and the underlying object has IsValid set to false.

If then the behaviour is re-enabled due to OtherComponent gaining authority, receiver will be re-injected, but IsValid will not be set to true.

This is the same bug as #1326, but for the sender rather than the readers. The fix is to have everything implement IRequireable. This is a consequence of #1297 where we changed the behaviour of behaviours with multiple requireables.

Tests

Test cases for reader/writer/commandsender/commandreceiver

Documentation

• Changelog

[zeroZshadow]

Should this check if the captured command sender/receiver is invalidated?

[jamiebrynes7]

Those are captured in https://github.com/spatialos/gdk-for-unity/blob/develop/workers/unity/Assets/Tests/EditmodeTests/Correctness/Subscriptions/RequireablesDisableTests.cs :)

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication