Wojciech Trocki

## Feature Request **Is your feature request related to a problem? Please describe.** Please describe the problem you are trying to solve. **Describe the solution you'd like** Please describe the...

version is duplicated when using schema as input for datastore CLI

1

## Feature Request

Rewrite queue id after create operation using server side id

3

## Feature Request

## Feature Request Use find tasks returns error and data as any. Those should be strongly typed: ``` const { isLoading: loading, error, data, subscribeToMore } = useFindTasks({}) ```

## Feature Request We need ability to save some specific queries faster than full doc scan. For that we need secondary indexes.. https://developers.google.com/web/ilt/pwa/working-with-indexeddb#working_with_ranges_and_indexes Good demo to play with that adds...

Lack of insights into replication

2

## Feature Request ``` Rockstar react dev (noted from voice call) Replication is a black box. There is no way to receive any events or know about successful replication that...

As in title

## Feature Request Making any changes in the schema will break datastore - things will start failing in the background without any reasonable message - this should be caught before...

## Feature Request ``` Conversation from the call @wtrocki - you do not need to use datastore for every of your graphql queries now. You would do this for the...

## Feature Request When using datastore it is not clear if devs should still use cache/graphql clients in their app and hooks etc.