You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: crates/quarto-markdown-pandoc/CLAUDE.md
+14-5Lines changed: 14 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,10 +19,18 @@ need to be done with the traversal helpers in traversals.rs.
19
19
-**IMPORTANT**: When making changes to the code, ALWAYS run both `cargo check` AND `cargo test` to ensure changes compile and don't affect behavior. The test suite is fast enough to run after each change. Never skip running `cargo test` - it must always be executed together with `cargo check`.
20
20
-**CRITICAL**: Do NOT assume changes are safe if ANY tests fail, even if they seem unrelated. Some tests require pandoc to be properly installed to pass. Always ensure ALL tests pass before and after changes.
21
21
22
-
## Environment setup
22
+
## **CRITICAL**: HOW TO DO CODING WORK IN THIS REPO
23
23
24
-
- Rust toolchain is installed at `/home/claude-sandbox/.cargo/bin`
25
-
- Pandoc is installed at `/home/claude-sandbox/local/bin`
24
+
Whenever you start working on a coding task, follow these steps:
25
+
26
+
- Make a plan to yourself.
27
+
- The plan should include adding appropriate tests to the test suite.
28
+
- Before implementing the feature, write the test that you think should fail, and ensure that the test fails the way you expect to!
29
+
- Work on the plan item by item.
30
+
- You are not done until the test you wrote passes.
31
+
- You are not done until the test you wrote is integrated to our test suite.
32
+
- If you run out of ideas and still can't make the test pass, do not erase the test. Report back to me and we will work on it together.
33
+
- If in the process of writing tests you run into an unexpected parse error, store it in a separate file and report it to me. We're still improving the parser and it's possible that you will run into bugs.
26
34
27
35
# Error messages
28
36
@@ -44,6 +52,7 @@ After changing any of the resources/error-corpus/*.{json,qmd} files, run the scr
44
52
45
53
The `quarto-markdown-pandoc` binary accepts the following options:
@@ -52,8 +61,8 @@ The `quarto-markdown-pandoc` binary accepts the following options:
52
61
53
62
## Instructions
54
63
55
-
-in this repository, "qmd" means "quarto markdown", the dialect of markdown we are developing. Although we aim to be largely compatible with Pandoc, it is not necessarily the case that a discrepancy in the behavior is a bug.
56
-
-the qmd format only supports the inline syntax for a link [link](./target.html), and not the reference-style syntax [link][1].
64
+
-In this repository, "qmd" means "quarto markdown", the dialect of markdown we are developing. Although we aim to be largely compatible with Pandoc, it is not necessarily the case that a discrepancy in the behavior is a bug.
65
+
-The qmd format only supports the inline syntax for a link [link](./target.html), and not the reference-style syntax [link][1].
57
66
- Always strive for test documents as small as possible. Prefer a large number of small test documents instead of small number of large documents.
58
67
- When fixing bugs, always try to isolate and fix one bug at a time.
59
68
- When fixing bugs using tests, run the failing test before attempting to fix issues. This helps ensuring that tests are exercising the failure as expected, and fixes actually fix the particular issue.
0 commit comments