curator v0.3.4 Curator View Source

Link to this section Summary

Functions

active_for_authentication?(mod, user)

Verify a user is active for authentication

after_sign_in(mod, conn, resource, opts)

apply aftersign_in to _all modules

changeset(mod, fun, changeset, attrs)

Call a changeset on all modules

current_resource(mod, conn, opts)

deliver_email(mod, fun, args)

extension(mod, fun, args)

Call an extension on all modules

extension_pipe(mod, fun, args)

extension_reduce_while(mod, fun, args)

Apply fun to each module (until one fails). The fun must return :ok, or {:error, error}

find_user_by_email(mod, email)

guardian_module(mod)

opaque_guardian(mod)

redirect_after_sign_in(mod, conn)

sign_in(mod, conn, resource, opts)

sign_out(mod, conn, opts)

store_return_to_url(mod, conn)

Link to this section Functions

active_for_authentication?(mod, user)

Verify a user is active for authentication.

This will return :ok, or {:error, error}. The first error encountered will be returned, so the module order is important.

after_sign_in(mod, conn, resource, opts)

apply aftersign_in to _all modules

changeset(mod, fun, changeset, attrs)

Call a changeset on all modules

Similar to an extension, this accumulates a changeset across various implementations

current_resource(mod, conn, opts)

deliver_email(mod, fun, args)

extension(mod, fun, args)

Call an extension on all modules

This provides a way to coordinate actions between the modules, without them knowing about eachother directly. Each module can have verious extensions it broadcasts. The other modules decide if they’ll listen…

extension_pipe(mod, fun, args)

extension_reduce_while(mod, fun, args)

Apply fun to each module (until one fails). The fun must return :ok, or {:error, error}

TODO: Change this function name…

find_user_by_email(mod, email)

guardian_module(mod)

opaque_guardian(mod)

redirect_after_sign_in(mod, conn)

sign_in(mod, conn, resource, opts)

sign_out(mod, conn, opts)

store_return_to_url(mod, conn)