idea: should unify results act as memory variables saved to test env?
Open
Nobody has claimed this yet.
- Dominant language
- Clojure
- Stars
- 301
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
(tests
(PlaidClient (-> (env!) (select-keys [:plaid/client-id :plaid/secret])))
:= ?plaid)
(tests
((create-sandbox-token ?plaid "ins_129571") ! !)
% := {:public_token ?token :request_id _}
(println ?plaid ?token))
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by examining the tests macro and the env! usage shown in the issue, then trace how results move between test forms. Done would mean defining and documenting whether unified results become reusable memory variables in the test environment, with coverage for the illustrated ?plaid and ?token flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- clojure
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100