feature: support for cancancan

[u007]

Expected behavior vs actual behavior

anyway to pass in current_user, or current_ability from cancancan gem to determine the serialisable attributes?

Steps to reproduce

(e.g., detailed walkthrough, runnable script, example application)

maybe:
options = { ability: current_ability }
serialization = ActiveModelSerializers::SerializableResource.new(resource, options)

[cgmckeever]

@u007 this PR surprised me with the ability of getting the controller current_user
#1734

Maybe it will lead you down the path you need?

[u007]

@cgmckeever nice :)
when will this be main stream?

[bf4]

this is already present https://github.com/rails-api/active_model_serializers/blob/db87f8d85e7a46ef195a555cb7e2509f1affc622/docs/general/serializers.md#scope as serialization scope, no?

[cgmckeever]

I think it is already in the 0.10 branch. Which version are you using?

[bf4]

Or just https://github.com/rails-api/active_model_serializers/blob/db87f8d85e7a46ef195a555cb7e2509f1affc622/docs/howto/passing_arbitrary_options.md#passing-arbitrary-options-to-a-serializer

[u007]

nice, ive 0.10 :)