Andrea Peruffo
Andrea Peruffo
> some back propagation for the first case, correct? uhm, not sure I get this, do you have an example? > I'm a bit worried about the performance impact this...
> you'll need to check that all the following letters until the end of the string are uppercase to decided whether the underscore before the I is required or not....
Thanks for the feedback @sebastienlevert ! > the --ebc flag what's this?
Thanks for the link, yes I think that getting the new mangling behind a flag is not a big issue 👍
> which would mean in case the new rationale generated a different name for the same property, we'd add the property twice, with a deprecation notice on the original one...
What about a middle ground? We emit only one field, but, if you passed the ebc flag we mark the field as deprecated and craft an appropriate description for it?
correct
I started looking into this and I think that we should keep it for a breaking release. The fix is fine if we apply it to `StringExtensions.ToSnakeCase`, but the function...
I understand, it's fair, I think we can keep this on hold till we have a branch for version 2 of Kiota. Let me know if you want me to...
> What kind of documentation do you have in mind? Even a section in the Readme of the sub-module is fine by me. > The merge logic is stupidly simple...