Kyle

Hi there, I was just pruning my stale issues and PRs. I never heard anything from this PR and depended heavily on this working so I ended up writing my...

@jakub-bao FYI - if you need a workaround, look at @MeanMangosteen's comment above: https://github.com/s-yadav/react-number-format/issues/727#issuecomment-1617157506

@berk-can they most likely mean something like this: ```tsx export const NumberFormatWrapper: React.FC = (props) => ; ``` And then in places where you need the `NumericFormat` component, you'd instead...

@berk-can please show your code

@KodeMunkie were you ever able to solve the problem of mapping the calculated color palette to one of the 7 display colors? I am in the process of writing a...

Hey @baywet, Thanks for your speedy response! Unfortunately, a `type: "string"` and `format: "binary"` still produces the same `Task` signature: ```cs public async Task GetAsync(Action? requestConfiguration = default, CancellationToken cancellationToken...

That's an interesting question! Unfortunately it looks like it still ends up with a `Task` signature on the `GetAsync` function: ```json { "openapi": "3.0.1", "info": { "title": "WebApi", "version": "v1"...

Strange indeed! Here's my version output: ``` > kiota --version 1.8.2+212af8870aec683004cecc17f1943c7a247bcfa7 ``` I'll try tweaking the unit test to see if I can get it to fail. I'll let you...

Something hinky is definitely going on here. I'm still digging, but it looks like the C# code method writer will handle `"binary"` correctly (in `CSharpConventionService.TranslateTypeAndAvoidUsingNamespaceSegmentNames`) as it will generate a...

I figured it out! This happens because my API spec has a `200` status code that returns binary data but the `400` status code returns JSON! If I remove the...