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

curl --location --request POST 'http://example.com/api/test' \
--header 'Content-Type: multipart/form-data' \
--form 'file=@/C:/Users/Example/Pictures/index.png' \
--form 'name=test'

This is how you do multipart with http. This is for dio.

My presumption is that there should be a way to do this automatically as part of the release process.

I'm not 100% how best to achieve this, so before running with it I'd like to open it out for discussion.

To start things off, this SO question has a few answers/suggestions.

One suggestio

Hi! Kind of really impressed with your library ❤️

But I have some issues with UnknownField null values. It is reproducible with the following test

func TestUnknownFieldsProxyNullField(t *testing.T) {
	baseJson := `{"Field1":"123","Field2":null}`

	s := StructWithUnknownsProxy{}

	err := s.UnmarshalJSON([]byte(baseJson))
	if err != nil {
		t.Errorf("UnmarshalJSON didn't expec

It was not immediately obvious to me how I should reference types generated by codegen throughout my application.

When creating multiple queries that access different fields on a schema type, this can cause issues for fields required on the schema type, but missing in the query.

The documentation loosely shows how to destructure a query result to use the inner objects, rather than using the

According to https://www.weld.rs/grizzly/ the command to get started is $ pip install grizzly however this doesn't seem to be correct. The grizzly package on PyPi is some sort of USB driver.

I believe the documentation should be: pip install pygrizzly but that is failing for me, too

The Khronos reference page contains description of parameters and description of the behavior for every function. Wouldn't it be possible to add doc comments for the functions, so IDE can show it? I understand the function description is a bit cumbersome, as one description is usually related to multiple functions with similar functionality, however parameters description would help a lot.
I am c

Various linting tools will throw an error if an anonymous import isn't documented with a comment.

Something like:

import (
    "fmt"
    "log"

    // Import the MySQL driver for database/sql.
    _ "github.com/go-sql-driver/mysql"
)

Is this possible using Jennifer?

Is your feature request related to a problem? Please describe.

No MappedTypeNode definition in ts-morph.
No TypeQueryNode definition in ts-morph.
No TypeOperatorNode definition in ts-morph.

Consider porting existing PeachPy Go projects to avo. At a minimum this would be really valuable feedback and system-level testing for avo. These could be committed to the avo examples directory or potentially committed back to the original repos if their maintainers are interested.

inline templates:

• with anonymous classes
• with lambda

[docs] Using the phrase "The Drupal CLI" is misleading

Problem/Motivation

The language "The Drupal CLI" is misleading. It implies that this it the only Drupal CLI, or is in some ways more official than other Drupal command line tools. This is present in the repo configuration and the readme, possibly in other places too.

Details to include:

• Why are we doing this? Above all, a

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

One line summary of the issue here.

Building the scrooge-linter fails because the 19.10.0 version of the util-logging dependency cannot be found. Changing build.sbt to use 19.9.0-SNAPSHOT works fine

Expected behavior

A command like the following should run:

./sbt 'scrooge-linter/runMain com.twitter.scrooge.linter.Main --help'

In this case, this should display the linter's

We should add a new argument type for buffers that are used as both input and output. Also documentation for buffer constructor needs to be updated. The code generator should also be modified.

In the CPU code generator that uses Halide there is not difference between input, output and input/output buffers. They are all treated in the same way, but for generating GPU code, we want to be able to

The existing docs only contain basic usage guide for Opti(). It will be nice if more docs are provided for Opti stack, especially for to_function and options.

Could either check a version parameter in each, or possibly use a hash over each ttinclude files to check everything is as it should be.
cc @ErikEJ

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.

A biexponential synapse, as per the Brian 2 documentation, should implement a current/conductance as g(t)=(tau2/(tau2-tau1))*(exp(-t/tau1)-exp(-t/tau2)).

When playing around with the biexponential synapse concept, I found that maybe the above description might need to be updated. Consider

import matplotlib as mpl
mpl.use('Agg')
import pylab as pl

import numpy as np
from b