-
-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start of refactor to turn maverick into a plug library #25
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How are you planning on using the Api
module defined by the user's use Maverick.Api
as its own plug? I had pictured this module as the place where you define your application's full Plug pipeline, so having the Api be itself callable as a plug is making me wonder where you'd include that?
end | ||
end | ||
|
||
describe "ssl" do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we comment these out so we know to refactor them to accommodate how Plug lets you set up a server using SSL?
Module.register_attribute(__MODULE__, :maverick_routes, accumulate: true) | ||
Module.put_attribute(__MODULE__, :maverick_route_scope, unquote(scope)) | ||
|
||
@on_definition Maverick | ||
@before_compile Maverick | ||
|
||
def call(%Plug.Conn{private: %{maverick_route: route}} = conn, _opts) do |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
dammit, that's inspired
46d6473
to
8e2d0ae
Compare
No description provided.