Stanislav Kupryakhin

@phryneas Sorry, I should've explain what's expected. I see two options: 1. Simply generate ```typescript export type User = { id?: number name: string } ``` 2. Generate two different...

Typescript `readonly` is basically a different thing. Here's a description of readonly in [OpenAPI specs](https://swagger.io/specification/): > readOnly: boolean Relevant only for Schema "properties" definitions. Declares the property as "read only"....

So generating two types seems to me like a more "proper" design according to OpenAPI spces, but it also may be harder to implment.

> Generally though this reads more like these should just be optional, not readonly - at least from our perspective. Yes, that's right, it's more like `optional` on RTK Query...

From the doc: _'g:miniBufExplBRSplit'_ To control where the new split window goes relative to the current window, use the setting: let g:miniBufExplBRSplit = 0 " Put new window above "...

There are some JS large numbers libraries, like https://github.com/MikeMcl/big.js/ The main issue that JS has no operator overloading. Because of that fact, these libraries have additional methods for each math...

Probably, some trick may be implemented - when we detect input values that overflow JS Number, it is scaled down, and all the math is performed with scaled down values,...