Proposal: Namespace methods according to respective Proto file about rust-server HOT 2 CLOSED

Generally I would go with the simplest thing and just prefix like net_getPlayers.

However in this particular case I wonder if we shouldn't instead change the API names to be a bit more specifically accurate. coalition.getPlayers was named as such because that was the ED name.

However, especially in light of the conflict above, I wonder if we should rename this to coalition.getPlayerUnits since it is actually a more accurate representation of the data being returned which is in contrast to the data being returned by net.getPlayers which is more about the player than the unit.

from rust-server.

I wonder if we should rename this to coalition.getPlayerUnits since it is actually a more accurate representation of the data being returned which is in contrast to the data being returned by net.getPlayers which is more about the player than the unit.

Good observation. I will integrate that in a PR to come shortly.

This morning, I thought of a lightweight solution to detect conflicts in registration. What if we had functional registrations such as

GRPC.registerMethod('theMethodName', function(params)

end)

If there is already another method, deregister both methods. That way the person who is writing a new function would be forced to acknowledge the duplication.

The only other alternative is to perform a full regression test suite, which is very heavy given for full confidence, we need to launch DCS on a CI build (ouch!)

from rust-server.