What do I use in place of 'createCanBoundTo()'

[shepnorfleet]

REF: in version 5 of '@casl/react' the createCanBoundTo() function was removed

Q: I was using that function to create a Can attached to my application-wide context. How should I proceed given the new paradigm?

[shepnorfleet]

I see the BoundCanProps are still present in Can.ts in 5.0.

Trying to figure out how to implment a bound Can using my ability in the application context. Any thoughts?

[shepnorfleet]

It looks like the base Can class component can change its ability subscription after the fact, yet the methods to do so are private.

[shepnorfleet]

I am not well versed in class components as I am in function components; so I might be missing something obvious here.

[shepnorfleet]

I guess it should be stated that I really don't want to create a separate application-wide context just for the Can.

[stalniy]

You need to use createContextualCan. createCanBoundTo was added to support version of react which doesn’t support contexts

this is written in docs.

[stalniy]

I removed it to simplify API and drop support for older react versions.

the better approach is to use useAbility, it’s better from casl performance standpoint. Smaller amounts of subscriptions to ability changes. Also using context api gives you a way to substitute ability instance in tests and see how your component behaves on different permissions definitions.

Though you still can add a simple functional wrapper around

const ability = createMongoAbility()
const Can = (props: BoundCanProps) => <AbilityCan {…props} ability={ability}>{props.children}</AbilityCan>

[shepnorfleet]

Thank you very much ... going to try this now :)