Martin DeMello

feature request: a skeleton project

40

Could you add a repo with a small skeleton project, with the javascript pipeline (bundler, watcher etc.) configured and working? It would be a big help for people not coming...

request: support for ocaml-vdom's ui api

3

Lexifi's [ocaml-vdom](https://github.com/LexiFi/ocaml-vdom) has a nice API for declaring UIs, similar to elm's but nicer in a bunch of small ways. It'd be great to have that as an alternative API...

I've added a simple cgi test server so that the cgi aspect can be tested without having to set up a webserver. Also, I couldn't get it working with cgi...

Document the "no method named `system` found for fn" error

2

Getting the wrong signature for a function leads to a complex error message like ``` error[E0599]: no method named `system` found for fn item `for fn(&'r mut bevy::prelude::Commands, &'s mut...

config should be a global constant

3

We currently pass the config struct around all over the code; however, it contains paths to resources and as such is a property of the local environment, not a runtime...

add a link to the esm module docs in the guide

1

This [issue with vite](https://github.com/revolist/revogrid-react/issues/6) is not react specific, and is fixed by following https://github.com/revolist/revogrid/blob/master/docs/custom.element.md There is a section in the README about that, but the doc should be either linked...

document the cell renderer in more detail

3

It would be helpful if the cell renderer documentation included some more details about the callback function, something along the lines of: The `props` argument provides access to the column,...

The documentation currently links directly to `https://github.com/revolist/revogrid/blob/master/src/interfaces.d.ts`. A typedoc-generated html file would be friendlier, and specific types or sections could be linked to from various other places in the documentation.

Add a bounding box class to store dimensions and anchor.

5

Reworks a bunch of property update code in Actor to use a bounding box. This is a refactoring en route to supporting more transformations (flipping, scaling).

there are several boolean options in libcst's `ApplyTypeAnnotationsVisitor` to tweak the annotation merging behaviour: ``` overwrite_existing_annotations: bool = False, use_future_annotations: bool = False, strict_posargs_matching: bool = True, strict_annotation_matching: bool =...