Roman Mahotskyi

Hi @Orcioly, it seems that you need to create a unique ability instance for each HTTP request. Usually, you can do it in middlewares which have access to the current...

> The issue is that GraphQL will not be used in this project CASL `AbilityBuilder` is not bound to the concrete implementation > My intention is really to do it...

In the first example I showed how to configure CASL and let ability builder to be aware of the current user (who is requesting data). In second example I showed...

Hi @Orcioly > const accessTokenPayload = await authenticationService.validate(accessToken) where is this validity coming from? In my example, this line of code ```typescript ... const accessTokenPayload = await authenticationService.validate(accessToken) ... ```...

I also can confirm that `isaCheck` doesn't work as expected in 0.26.0 (node.js). If I rollback to the version 0.25.1 my code works correctly.

@piotrwitek any updates?

I have the same issue. The `onCompleted` hook is not triggered after sending query with same variables. ```typescript const [lazyQuery] = useLazyQuery(QUERY, { onCompleted: () => {...} })` lazyQuery({ vairable:...

I also have such problem in my code I was trying to use it like ```ts const carouselRef = useRef(); ^^^^^^^^^^^ - shows warning ```

> I find a way . Just wrap the `ReturnType` with `Immutable.Record` > > ```js-jsx > // src/store/index.ts > import { Record } from 'immutable' > import { combineReducers }...

I also have problems with label duplications in v5 (I didn't tested it with v4). It shows me a warning in a console ``` index.js:1 Warning: Encountered two children with...