Version 3.4.0 and reactive return types

[laurentpellegrino]

Using version 3.4.0, when a method annotated with @command returns for example a Mono, it does not automatically subscribe to the reactive instance. Instead, it seems to call toString on this object instance. Is there no support for reactive types with spring shell?

[fmbenhassine]

That's one of the issues/confusions this reactive stack is bringing.. I could not find context about the need to introduce reactor in Spring Shell, but I see no need for the reactive stack in a shell app (as mentioned here #1205 (comment)). Thoughts?

[piotrooo]

TBH, I also think that using reactive is incorrect, and there’s no reason to use it anymore.

[fmbenhassine]

Thank you for your feedback, @piotrooo! This reminds me something similar with SSM, see spring-projects/spring-statemachine#1080 (comment). I created #1213 to revisit the dependency to reactor, and I will see if we can include it in v4 (which I am really looking forward to from a long term maintenance point of view).

[fmbenhassine]

@laurentpellegrino

Using version 3.4.0, when a method annotated with @command returns for example a Mono, it does not automatically subscribe to the reactive instance. Instead, it seems to call toString on this object instance.

This seems like a bug in v3.4. If you manage to have a reproducer, please open an issue in favor of this discussion.

Is there no support for reactive types with spring shell?

This might come in v4, see #1213.