romalytvynenko
romalytvynenko
@rcerljenko Nice, thanks! If you can create a repro repo that I can simply install and get this issue – this also would be great 😊
@dmason30 **should** be fixed in [v0.10.7](https://github.com/dedoc/scramble/releases/tag/v0.10.7)
@Jens-dev can you show some examples of your code base as well?
@jcsix694 thank you! That's enough info, and I will fix it
@jcsix694 good question. Can you try `0.8.5` and check if it works? A lot has been done so this can actually work, but I'm not sure.
@jcsix694 hey. Sorry for late reply. While I've substantially improved type inference since you've created the issue, I can see that the real reason Scramble does not understand this specific...
@kichetof **should** be fixed in [v0.10.7](https://github.com/dedoc/scramble/releases/tag/v0.10.7)
@vszambon1 true! Thanks for reporting. I also can see that response structure in general is not correctly documented in such case? Because expected structure is array, `{message: string}`, not just...
Oh, okay. So, I'll fix only constants 👾
Hey @dmason30 This is a problem indeed, however I'm not sure how to solve it. So the reason here is not only the question mark, but Open API spec itself...