-
Updated
Sep 6, 2021 - TypeScript
codegen
Here are 425 public repositories matching this topic...
One of the specific advantages of the wire approach is that it generates code that's relatively readable compared to reflect-based equivalents. When wire.Value is used on a small by-value type, there's no need for the value to live in a global variable - the expression could instead be used literally inside the generated code, which would make the code easier to follow, and more similar to the c
-
Updated
Aug 25, 2021 - Swift
-
Updated
Sep 1, 2021 - JavaScript
-
Updated
Sep 1, 2021 - TypeScript
-
Updated
Mar 9, 2019 - JavaScript
-
Updated
Jul 12, 2021 - Swift
-
Updated
Aug 23, 2021 - Go
-
Updated
Sep 6, 2021 - TypeScript
I do most of my development against 2.12 because of sbt, but during CI we still build against 2.13 to test both the generator as well as the generated code against 2.13.
As a result, a lot of warnings have appeared around deprecated syntax and deprecated stdlib imports, these should be resolved.
This is a fairly straightforward change, you can see some of the warnings by doing
sThe Generated Client API is remains largely undocumented...
It would also be awesome if we could include the documentation of the API in the Generated DSL
-
Updated
Dec 4, 2019 - C++
Reason/Context
The problem is described here asyncapi/playground#79. It must be clear that returned data is not content but an object with content and metadata + what is this metadata, and that it is only with React renderer.
Description
Probably JSDoc must be only updated. Of course, some additional section in the readme would be also welcomed
-
Updated
Sep 6, 2021 - Swift
-
Updated
Apr 27, 2021 - Go
-
Updated
Oct 5, 2020 - Kotlin
-
Updated
Mar 19, 2021 - Rust
See the documentation of the config file format.
The current state of existing configs (click to expand).
-
Updated
Apr 13, 2021 - Go
Improve this page
Add a description, image, and links to the codegen topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the codegen topic, visit your repo's landing page and select "manage topics."


Is it possible to specify a complexity limit that doesn't apply to schema introspection? Or to manually set the complexity cost for schema introspection?
I took a look through the generated code, but didn't see any hooks relating to this (I may very well have missed it).