Affects: 5.3.21
There is a typo in org.springframework.web.socket.config.annotation.SockJsServiceRegistration#setSupressCors: the method should be named setSuppressCors.
Comment From: sdeleuze
@rstoyanchev Should we use the opportunity of 6.0 to deprecate setSupressCors and introduce setSuppressCors, or even more aggressively just rename it and mentioning it in release notes?
Comment From: rstoyanchev
A deprecation + a new method sounds good to me. It could even be done in 5.3.x since it allows for a migration period and is easy to change if you get a build warning.
Comment From: sdeleuze
If we do deprecation + a new method in 5.3.x, is it fine from your POV if we just keep the new method in 6.0?
Comment From: marcwrobel
@sdeleuze, I have created a PR against 5.3.x for this issue. I marked setSupressCors as deprecated for removal in 6.0 (@rstoyanchev seems OK with your reasoning).
Comment From: snicoll
Thanks @marcwrobel. Closing in favor of PR #28853