Dawson Booth

@KyleKing I just ran into the same issue. It turns out that TOML doesn't usually allow multiple separate types and you can't have ```toml [tool.portray.mkdocs] markdown_extensions = [ ... ]...

We're running into this as well, and it seems like the only way forward is to change how our spec is produced from the backend, which is less than ideal...

It seems that the problem comes from orval appending "Item" to the generated list item type, but since we already have a name being generated with the item suffix TypeScript...

I believe this is the offending line: https://github.com/anymaniax/orval/blob/89368eacca8225820ab1195052ffe858b7074507/packages/core/src/getters/array.ts#L23 The "Item" text here should be configurable IMO

Already getting familiar with the codebase :) I'll see if I can find time to put something up soon, but anyone who's contributed before feel free to beat me to...

We addressed this issue by removing the `useInfiniteQueryParam` global setting, wrapping the generated query hook, and building our own `queryFn` to override the generated one. This lets us have separate...

@pycraft114 Sure! Sorry, just now seeing this. Our case had to do with using a timestamp cursor to fetch an infinite list of notifications. Instead of messing with the infinite...

~~I was running into a similar issue that's related to this; updating one field that is nested under array did not update the array state. But, after adding an `onChangeListenTo`...

I thought it would help if I added that I get a similar error when parsing a file. Here's the traceback: ```python >>> from slippi import Game >>> Game("D:\\OneDrive\\Gaming\\Melee\\Slippi\\Error\\Game_20200615T235839.slp") Traceback...

Would love to help out where I can here since I need this same change soon. Any good place for me to start?