Make current_tenant thread safe

[wireframe]

Thank you for your contribution! The code addition is super straightforward, as expected. The real trick is on the testing side. My recommendation is to simplify the testcase such that the new thread attempts to overwrite the current tenant variable. There are some good examples available here: https://stackoverflow.com/questions/6241384/how-do-i-manage-ruby-threads-so-they-finish-all-their-work

describe '#current_tenant=` do
  it 'is threadsafe' do
    Multitenant.current_tenant = :old_tenant
    overwriter = Thread.new { Multitenant.current_tenant = :new_tenant }
    overwriter.join
    expect(Multitenant.current_tenant).to eq :old_tenant
  end
end

[sapanakothari]

Thank you for your contribution! The code addition is super straightforward, as expected. The real trick is on the testing side. My recommendation is to simplify the testcase such that the new thread attempts to overwrite the current tenant variable. There are some good examples available here: https://stackoverflow.com/questions/6241384/how-do-i-manage-ruby-threads-so-they-finish-all-their-work

describe '#current_tenant=` do
  it 'is threadsafe' do
    Multitenant.current_tenant = :old_tenant
    overwriter = Thread.new { Multitenant.current_tenant = :new_tenant }
    overwriter.join
    expect(Multitenant.current_tenant).to eq :old_tenant
  end
end

Thankyou for your review and feedback. Changes are incorporated, kindly give another go.

[wireframe]

Thank you @sapanakothari for your contribution! This has been merged and released in the v1.0.0 release.

[sapanakothari]

Thanks @wireframe!