The Wayback Machine - https://web.archive.org/web/20210907020708/https://github.com/topics/codegen
Skip to content
#

codegen

Here are 425 public repositories matching this topic...

rogpeppe
rogpeppe commented May 25, 2019

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

blast-hardcheese
blast-hardcheese commented Sep 2, 2021

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

s
derberg
derberg commented Feb 10, 2021

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 😄

Improve this page

Add a description, image, and links to the codegen topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the codegen topic, visit your repo's landing page and select "manage topics."

Learn more