Chris Atkin

I'm afraid not - this library doesn't have an active owner anymore.

As @willbamford has mentioned on https://github.com/JSainsburyPLC/react-timelines/pull/103#discussion_r287817534 >I'm not sure you can rely on this as tracks can be dynamically loaded i.e. only loaded in when you hit toggleOpen (could be...

Sorry there's no API documentation for the components - the library is largely unmaintained at the moment. A [demo is included](https://github.com/JSainsburyPLC/react-timelines/tree/master/demo), that was originally written to showcase the timeline internally....

For anyone coming to this from Redis, I think the pattern you use is dependant on the client you're using. For example, if using `ioredis`, your pattern is ultimately used...

I'm getting the same error when using `@apollo/react-hooks: 3.1.3`, `react-apollo: 3.1.2` and `@apollo/react-testing: 3.1.2`. I have a component containing `Query`. This works at runtime, nested within `ApolloProvider`. This throws the...

Awesome, look forward to seeing how workspaces evolve. We'll keep loading the workspace specific variables with `-var-file=staging.tfvars`.

>Is this still valid or the context is other @gudata & @beingamarnath - workspaces are still a very valid way to manage multiple environments in many scenarios. However, workspaces share...

The tests are failing on Node 12, but not on earlier versions (on Travis and local). Is this related to https://github.com/zalando/tailor/pull/322?

I think `requestFragment` needs the initial `filterHeaders` function. If it's passed in `options`, it won't be called with `filterHeaders` - it'll just be assigned over it. https://github.com/zalando/tailor/blob/571b6d545e99957705c507cdba09a6c0c2871985/index.js#L65-L81 If having the...

Having multiple module requires (`-r`) in `NODE_OPTIONS` is permitted; they'll each get required when your code starts, before Next.js is invoked.