custom `expectedResponse` not working when using Combine publisher mode about connectivity HOT 6 CLOSED

@rwbutler Ah yes ! that works, just stumbled across case .custom: validator = customValidator and realized that must be the missing param. Thanks for your time!

from connectivity.

@zenghaojim33 Thanks for flagging - I'll look into this!

from connectivity.

Hi @rwbutler I tried with the latest version ( and I found the bug in the previous version during the day ). Turns out that the validator factory is not taking the expectedResponseString from the one passed into responseValidator, but the one declared in Connectivity class. Later in manufacture() it returns a new validator with that default value. Didn't look into it but I assume that same behavior will happen to expectedResponseRegEx as well. Now I am switch to original usage and explictly assign the value which works for me.

from connectivity.

@zenghaojim33 If you change the validationMode to .custom things should start working. Currently, custom validators are only used when the validationMode is set to .custom. Let me know if this works for you!

from connectivity.

@zenghaojim33 Just saw your latest comment - setting the value of expectedResponseString and using a validationMode of .containsExpectedResponseString should also work as you say.

from connectivity.

@zenghaojim33 No problem! Glad that worked for you 😃

from connectivity.