hyperfiddle / hyperfiddle/rcf

No way to check ex-data on an error

Open
#80 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Clojure
Stars
301
Forks
14
PR merge metrics
No merged PRs in 30d

Description

(tests
  (throw ...) :throws Exception
  (ex-data *e) := ...)

https://clojurians.slack.com/archives/C7Q9GSHFV/p1694471863365209

Should *e be bound by :throws ?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No file or test path is named. Start by tracing the :throws handling and the ex-data/*e behavior in the RCF test macro, then determine whether errors expose the needed data there. Done means the proposed form has defined behavior and coverage for checking ex-data after a thrown exception.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
testing
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.