Tomasz Cichocinski

Provide morph-logger module

2

It would be amazing to have some basic logging middleware available out of the box. Maybe not something fully featured like https://github.com/expressjs/morgan but basic logger middleware from https://github.com/reason-native-web/morph-hello-world-pesy-template/blob/master/library/Middleware.re would be...

Move GraphiQL.re from graphql template to morph-server-graphql

3

It would be great to provide `~graphiql: bool` option to `Morph_graphql_server.make` or provide something like `Morph.Response.text(Library.GraphiQL.html, Morph.Response.empty)` available from `Morph_graphql_server` module / cc @cem2ran

feat(morph_logger): basic implementation

1

Resolves: #25 Basic logger implementation based on https://github.com/expressjs/morgan. Not sure if we want this but seams pretty extensible accepting `Custom(list(token))` format allowing us to add more tokens in the future....

It appears node mutations are randomly omitted from incremental snapshot

3

On the following demo website `rrweb` fails to record `Toolbar` element: - CodeSandbox: https://codesandbox.io/s/jam-sandbox-299kuq?file=/pages/index.vue - Demo: https://299kuq.sse.codesandbox.io/ Here is the HTML of the element. ```html Toolbar ... ``` Sometimes (I...

Not sure if it's the correct approach. It allowed me to move forward. It another approach is required, I'm keen to improve 🙂 Would fix #165

ExportFinder > Cannot export twice

1

Hi! Amazing work on fastpack. It would be amazing if I could use it in production applications but my quite large codebase fails because of `ExportFinder > Cannot export twice`...

There are really no benefits from using monorepo for `reason-expo` as it's just a single set of bindings. Flattening out project structure and removing template/test (at least for now) would...

Rely: pretty printing boolean values

5

Right now when doing: ```reason expect.equal( {userId: 1, id: 3, title: "fugiat veniam minus", completed: false}, {userId: 1, id: 3, title: "fugiat veniam minus", completed: true}, ); ``` we receive...

Changes `StackNavigator.Screen` from `statelessComponent` to `statelesscomponentWithRetainedProps`. It allow us to check for header props changes and call `navigation.setOptions` when they change. Only problem are properties that are recreated every time...