Github Actions should also test building documentation for pushes and pull requests to check for broken docs. Seems like there is a Docker container for that: https://hub.docker.com/r/readthedocs/build/

This stackoverflow post outlines a different method of using namedParameters than the readme and seems to be correct. Readme could be updated to match.

https://stackoverflow.com/questions/6212219/passing-parameters-to-a-bash-function

As it currently stands, the deferred initialization of a ghost object (as per documentation) looks quite messy:

$initializer = function (
    \ProxyManager\Proxy\GhostObjectInterface $ghostObject,
    string $method,
    array $parameters,
 

I am getting Unexpected keyword argument mypy errors for my slightly modified attrs' dataclasses on latest attrs 19.3.0 and mypy 0.740. It took me some time lurking docs and github issues to realize there's no plugin I forgot to add, just mypy fails to recognize attr.s after I've wrapped it like this:

def dataclass(cls):
    cls = attr.s(kw_only=True, auto_attribs=True)(cls)
    cls.__at

We need a contributing.md doc that shares community conventions.

Stamp conventions

• Naming stamps: your-module-name-stamp
• Keywords for package.json: stamp, stampit

Automatic code quality conventions 😎

• Use the prod-module-boilerplate (soon to be replaced with `npm install -g cloverfield cf-package

The navigation in the documentation is currently showing a horizontal scrollbar and isn't full-height.

I'm not sure if it's supposed to be full-height, but I think the horizontal scrollbar should be an easy fix by just making it slightly wider ;)

Here's a screenshot to show what I mean:
![capture](https://cloud.githubusercontent.com/assets/152227/14913804/d8c2c74c-0e05-11e6-92f5-3e2d97904e92.PNG

I'm submitting a bug where logAction does not log actions accurately in redux dev tools

[ ] Regression (a behavior that used to work and stopped working i

I'd like to contribute when I can, but it's hard knowing your intentions for parts of the application that haven't been completed yet.

Could you provide a document that gives the design of the application? A good and simple format to begin with is:

Class

This is a description of a school's class. It does this and that ... Its properties are:

• Property 1
• Property 2

Section

Let's improve the documentation about TeeInput and TeeOuput classes. For example:

1. How can I copy an Input to Output?
2. How can I copy an Output to Output?
3. How can I copy an Output to Input?
4. How can I convert an Output to Text?

Instead of using pngs, use svg files and remove pngs altogether

Is there any plan to support the new v3 Checks API?
https://developer.github.com/v3/checks/

The current documentation lacks information on dependency injection and best practices for doing so. Also, it misses to point out that only constructor level injection is being supported and it also misses to point out why, at the test method level or lifecycle hook level, no injection can take place.

It also misses information on the available DI containers, and why one should not make the tes

The B-Prolog 8.1 native random number generator returns random integers, both positive and negative, with no documentation on their range. Given that B-Prolog also claims that its implementation of integer arithmetic is unbound, we cannot use its native random number generator as basis to generate random numbers in a given interval.

Low level documentation could be generated from jsDoc. We need to find a good module able to handle this for each sub-packages.
Generated documentation should be easily readable, display all informations present in jsDoc and have links to other files (for types for example).

PS: High level documentation ("readme", "first steps", "changelog" ...) should still be written by hand.