ptupitsyn commented on code in PR #10145:
URL: https://github.com/apache/ignite/pull/10145#discussion_r922215698
##########
modules/platforms/dotnet/Apache.Ignite.Core/Impl/Services/Services.cs:
##########
@@ -501,6 +501,16 @@ private static void
ValidateConfiguration(ServiceConfiguration configuration, st
IgniteArgumentCheck.NotNull(configuration, argName);
IgniteArgumentCheck.NotNullOrEmpty(configuration.Name,
string.Format("{0}.Name", argName));
IgniteArgumentCheck.NotNull(configuration.Service,
string.Format("{0}.Service", argName));
+
+ if (configuration.Interceptors != null)
+ {
+ IgniteArgumentCheck.Ensure(configuration.Interceptors.Count >
0,
Review Comment:
I think there is no reason for this restriction, it just makes the life
harder for the users. There may be an edge case of some sorts on their side.
Let's just treat null and empty the same way.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
