Question 1

How do I handle permissions for nested resources with ember-can?

Accepted Answer

Ember-can supports passing additional attributes to abilities. For nested resources, use extra properties in helpers or service calls, like `(can 'edit post in project' project member=member)`, and access them in the ability class for complex checks.

Question 2

Ember-can vs ember-simple-auth: what's the difference?

Accepted Answer

Ember-can focuses on authorization (permission checks), while ember-simple-auth handles authentication (login/session management). They are complementary; use ember-simple-auth for securing routes and ember-can for fine-grained access control within the app.

Question 3

How to test abilities in an Ember app using ember-can?

Accepted Answer

The addon generates unit tests for abilities via blueprints. For integration tests, stub the abilities service following Ember's official testing guides, as mentioned in the README, to mock permission states.

Question 4

Can I use ember-can with Ember Engines?

Accepted Answer

Yes, but you must re-export abilities in the engine's namespace to make them accessible, as detailed in the 'Accessing abilities within an Ember engine' section, which adds some setup overhead.

Question 5

How to upgrade ember-can without breaking my app?

Accepted Answer

Check the UPGRADING.md file in the repository for version-specific migration steps, as breaking changes between versions may require updates to ability classes or setup code.

Question 6

What's the best way to inject a custom session service into ember-can abilities?

Accepted Answer

Inject your session service directly into ability classes using Ember's @service decorator, as shown in examples, to access user data for permission logic without tight coupling.

ember-can

What is ember-can?

Overview

Use Cases

Best For

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions