palkan/action_policy-graphql

Make field extension more flexible

palkan opened this issue · 0 comments

palkan commented

There are some scenarios which are not currently covered:

  • Calling authorize! before resolving field (see #6)
  • Calling both authorized_scope and authorize! on the same field (see #8)