codeconsole commented on PR #16149: URL: https://github.com/apache/grails-core/pull/16149#issuecomment-5513926472
> @codeconsole We've been removing deprecations every release. I do not agree with it's deprecation or removal. I'm objecting to changing a public API that's been there since Grails started. I'm asking to revert the caller renames to simplify this diff since they are unrelated to the issue being fixed. I am trying to understand why don't you agree with its deprecation or removal. Give me a use case. Please help me understand why you want something other than "just because it has always been there" If the only reason of it being added in 2009 was for multi-part and this PR addresses request performance and eliminates the multi-part path, how is it unrelated? Is it performant to call a proxy method that does nothing? Please just give me a single use case how keeping it valuable or settle on a compromise of keeping the rename and removing the `@deprecated`. I am fine with that. We can keep the method for another 10 years, but I don't see the reason why we can't have the other callers go direct instead of proxying for something they no longer need? -- 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]
