Fix issue with missing rename of Self_

[jwiesler]

Summary

See #489.

The issue is that serde's snake case for enum variants differs from heck's snake case, especially for Self_ (and one more unexpected case, see the diff).

This was fixed by including the function used by serde, which is sadly not exported so I copy pasted it (serde is under MIT license).
The issue here is obviously that serde may change the internal function but I think this is very unlikely since it breaks all parsing code in existence and serde is no longer in alpha :)

Checklist

• ran cargo make fmt
• using conventional commits to hightlight user-facing fixes and features

[jwiesler]

@arlyon

[arlyon]

Running CI now, thanks!

[arlyon]

Closes #489

[arlyon]

I think we should probably just strip the trailing underscore or rework the Self case to use raw identifiers like r#Self

[jwiesler]

I think we should probably just strip the trailing underscore or rework the Self case to use raw identifiers like r#Self

For Self this might solve the problem, but as you can see above the two implementations even differ in other places, this is just waiting for bugs to appear. There is no testing to make sure the resulting renames generated by serde match the open api definition.

[jwiesler]

So just to make sure I've mentioned everything: The two implementations differ in:

• Trailling _
• _ before upper case character in the name
  We could patch the implementation from heck, but at this point this patch is as large as just copying the implementation from serde.

Furthermore the code relies on the two snake cases (what serde does and what we do to determine whether a rename is needed) aligning, otherwise we will output wrong renames or unneeded renames.

@arlyon could you please give an update on this or let someone else review this mr?

[arlyon]

Did some more digging and happy to merge this. Thanks!

[arlyon]

Apologies for the delay, we have a few very kind people who participate sometimes but usually when I am busy PR reviews stall. Thank you for taking the time.

[jwiesler]

Is there anything broken with the release pipeline? The crates.io version is stuck at 0.31 and we are at 0.33 in this repository already since three weeks? @arlyon

[arlyon]

Yeah, I need to manually push them. One of many things with this repo I've been meaning to get around to.