I've been using Sourcery to generate documentation automatically for GitHub wiki (i.e. generate markdown files based on types & annotations), as it's pretty user friendly on there (as in "easy to read") and also very easy to do in templates thanks to Sourcery's capability to generate files on the fly.

However, using annotations is not very "coder-friendly" though, as it gets hard to maintain be

Since typescript-generic-sdk got merged, we need to add docs, usage and examples.

Related: dotansimha/graphql-code-generator#2978

What happened?

Generated comment says , "The code below was going to be deleted when updating resolvers. "
But I exec gqlgen generate again, code didn't delete.

I don't understand when updating resolvers mean.

// !!! WARNING !!!
// The code below was going to be deleted when updating resolvers. It has been copied here so you have
// one last chance to move it out of harms 

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

It seems that someone edited out all documentation for SwaggerToTypeScriptClientGenerator.
Is is possible to revert back to older revisions to have it available for users?

https://github.com/RicoSuter/NSwag/wiki/SwaggerToTypeScriptClientGenerator#extended-classes-and-extension-code

when option dump-preprocessed-input is used, BINDGEN_EXTRA_CLANG_ARGS is evaluated AFTER handling dump-preprocessed-input which result errors like "head files not found" etc in cross-compiling.

We should add some links to Prisma examples in the README & docs.

This probably doesn't affect many people, and it isn't super important, but let's say you create a package with a name that is the same as a package it uses. Eg I might make github.com/xxx/myapp/http and inside of it use the net/http package.

package http

//go:generate moq -pkg http_test -out thing_moq_test.go . Thing

type Thing interface {
  Blah(w http.ResponseWriter, r *htt

I think it would be really helpful to also have the step by step guide to the kaleidoscope language with code for chapters separated, so you can see how it all comes together.

I'm willing to write it myself, if anyone wants to help that would be nice!

Weaver's documentation lacks guidance about how to solve dependency cycles.

The most common case is for delegate patterns, which can be solved by using a self reference.

Other types of cycles (ones described in #140) aren't allowed by Weaver, and the documentation should show how to work around them.

I see that x-server-raw-response is available to expose the underlying to users, allowing deeper customization of response.

I was wondering if it's possible to expose a similar interface for request as well? So that we can utilize some predefined functions by akka-http. For example, extractClientIP.

Not a huge deal and is blocking anything, since we can simply replicate all these funct

1. Add note about Android SDK/NDK installation #279
2. Add note about constructor = empty #280
3. Add note about clone/copy #274
4. Document SmartPtrCopy #282
5. Add into jni_tests/README.md note about ban for cross-compling
6. Add note about extension of "foreign" class/methods

As noted in #122, setting up AppSync debugging in a Carthage-based project is challenging. We need to provide some developer documentation around that workflow to make it easier for developers to debug AppSync if they suspect a problem with the SDK.

All examples and code I see assume there's only one .proto file. What is recommended way to compile .proto to .rs files, if we have thousands of input .proto files?

Example CLI command.

graphaello add https://apollo-fullstack-tutorial.herokuapp.com/ creates a camel case of the URL, I would like to use the API Name argument for CLI, but the documentation is not clear, how to use

See the documentation of the config file format.

The current state of existing configs (click to expand).