If the flow plugin runs before the class properties one (or if the class properties plugin isn't used), we remove uninitialize class fields:

class Foo { x: string }

currently becomes

class Foo {}

while it should be

class Foo { x }

If someone still wants the old behavior, they can either use flow comments (as [offically recommended](https://github.c

❌ to the ☕ script! ES6 is cleaner, more modern, and has a much more reliable linter—plus, people know how to read it—so we want to convert everything in the codebase. Most of the code is already there, but there are still specs written in Coffee.

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

#1947 landed a new t.try() assertion. It's experimental, one of the reasons for which is that we don't have documentation yet.

We need to document the assertion, how to use it and what the edge cases are.

Apologies for how bare this issue is — happy to elaborate more if you're looking to contribute this 😍

https://twitter.com/TheLarkInn/status/1056729742437543936
https://github.com/reactjs/rfcs/blob/gaearon-patch-2/text/0000-lazy.md

See:
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0
https://david-dm.org/angular-fullstack/angular-fullstack-deps/5.0.0?type=dev

Currently most (if not all) components' event handlers have the following typing: ((...args: any[]) => any);. This should be fixed and modified to the appropriate handler typing for each event.

TODO: List all components concerned and fix progressively.

• ...

It would be nice if there was documentation on how to use this with server side rendering.

Such that:

1. Server sends the prerendered compontent
2. Client receives the prerendered component and makes it interactive for the user

This issue is a:

• Bug report
• Feature request
• Question / support request
• Other

The Testing Section of the documentation seems lacking. More specifically, the Example Test section does not provide an appropriate example test, since it doesn't even de

I've used Poi in the past to for Vue projects, but just recently decided to try it out with react. The current documentation is almost completely devoid of any hints as to how to get started. I ended up using an older version of Poi to get up and running.

I think if this project wants to keep up with the other framework specific tools it needs to atleast document what's changed since v9~

I k

Validate the entire tree of options passed to preset.

Maybe, each plugin can export a list of options that only babili preset understands and we can validate them only when using the preset and not when using the plugin separately.

module.exports = function plugin() {};
module.exports.options = PropTypes.object({
  n: PropTypes.number
});

Or, this can be implemented in bab

legacyDecorators parser option should be documented.

It would be nice to see all the SQL queries sent to the server printed to standard Docker output (in development mode only).

More info:

• http://stackoverflow.com/questions/722221/how-to-log-postgresql-queries
• http://www.microhowto.info/howto/log_all_queries_to_a_postgresql_server.html
• https://chartio.com/resources/tutorials/how-to-log-queries-in-postgresql/
• https://docs.docker.com/