drugpl/bbq — Issue #24: TestUser vs. TestClient options attribute
Author: pawelpacana
Created: 2012-02-06 01:16:55+00:00
State: open

Currently `TestUser` exposes `options` attribute publicly. There are no clear use cases for me to have this method public. In fact this causes method conflict in `TestClient` where `options` is one of http methods actions.

In order to maintain consistency, TestUser can use `@options` ivar internally instead of accessor or we can rename accessor. This also means deprecating old `options` accessor.

What do you think?