Attach context

[joromir]

• Improve passing context to logger
• Refactor code in Loga::Configuration.

Fixes #77

[joromir]

👀

[bliof]

🤔 Unfortunately the current implementation won't do / needs expanding.

The main problem is that when we trace something e.g. sidekiq job or a rack request we want to pass some metadata to that trace e.g. Loga.context(user_type: 'Admin')

Overall we can refactor a bit more and extract the tracing so from e.g. Loga::Sidekiq::JobLogger#call and Loga::Rack::Logger#call when the trace starts we can create a context for that trace and with the Loga.context(user_type: 'Admin') we start filling that context.

# somewhere in Loga::Rack::Logger#call

Loga::Trace.trace do
   @app.call(env).tap { |status, _headers, _body| data['status'] = status.to_i }
end

# somewhere in the app

Loga.context(user_type: 'Admin')

# or even we can create nested traces/contexts

Loga.context(user_type: 'Admin') do
   Loga.logger.info "Call 1" # -> Call 1 user_type=Admin
   jobs.each do |job|
     Loga.context(job_id: job.id) do
        Loga.logger.info "Call 2" # -> Call 2 user_type=Admin job_id=123
     end
   end
   Loga.logger.info "Call 3" # -> Call 3 user_type=Admin
end

I'll continue the PR ☝️ direction. The dsl is still questionable ;)

[cassiomarques]

Closing, stale and probably no longer needed.

[bliof]

Needed but not trivial to implements so.. we haven't spend the time :) -> Opening again

[cassiomarques]

ivial to implements so.. we haven't spend the time :) -> Opening again

Would the code here be reused or would the author probably start from scratch?

[bliof]

No idea. If/when I try I'll use the current PR. Assume this PR as an Issue with some code :)