Conversation

brunokrebs

No description provided.

@mrlubos

@brunokrebs would you like to provide context?

@brunokrebs

Hi, @mrlubos, sorry, ended up opening to see if CI would run, but it didn't.

Anyway, before realizing that this repo is no longer maintained, I cloned it into my computer, added a test case, and generated the snapshot that shows what I was going to report.

As you can see, if we have an enum with keys like +name and -name, and +total and -total, the library ends up ignoring the "opposite" key (of whatever comes first, + or -).

so, on the snapshot, we ended up with:

export enum EnumWithStringsWithPlusAndMinusSigns {
    _NAME = '+name',
    _TOTAL = '+total',
}

Instead of a type with four keys.

@brunokrebsbrunokrebs marked this pull request as draft June 9, 2024 12:50
@mrlubos

@brunokrebs you got it with the deprecation notice. Feel free to open an issue in Hey API if this isn't fixed there yet.

@brunokrebsbrunokrebs changed the title opposite Missing Keys Jun 9, 2024
@brunokrebsbrunokrebs changed the title Missing Keys Missing fields on enum Jun 9, 2024
Sign up for free to join this conversation on . Already have an account? Sign in to comment
None yet
None yet

Successfully merging this pull request may close these issues.