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
I tried to add a long closing fence to an Instructor Note block (following the recommendation we put into the Style guide) and found that pegboard raises an error when a closing fence is more than 80 colons in length. Here's the error output:
── Validating Fenced Divs ─────────────────────────────────────────────────────────────────────────────────────────────────────
✖ A section (div) tag mis-match was detected.
✖ There are not enough close tags (5) for the number of open tags (7).
<error/purrr_error_indexed>
Error in `purrr::map()`:
ℹ In index: 22.
ℹ With name: 22-reflecting.md.
Caused by error:
! Missing close section (div) tag in /Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md.
Here is a list of all the tags in the file:
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:8 | tag: objectives
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:15 | tag: [close]
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:17 | tag: questions
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:21 | tag: [close]
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:32 | tag: challenge
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:39 | tag: [close]
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:48 | tag: instructor
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:61 | tag: :::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:63 | tag: discussion
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:80 | tag: [close]
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:99 | tag: keypoints
/Users/hodges/Documents/Carpentries/lesson-development-training/episodes/22-reflecting.md:104 | tag: [close]
---
Backtrace:
▆
1. └─httpuv (local) `<fn>`(`<externalptr>`, FALSE, "{\"pathname\":\"/\"}")
2. ├─base::try(handler(binary, message))
3. │ └─base::tryCatch(...)
4. │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
5. │ └─base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
6. │ └─base (local) doTryCatch(return(expr), name, parentenv, handler)
7. └─servr (local) handler(binary, message)
8. ├─ws$send(...)
9. ├─base::tryCatch(...)
10. │ └─base (local) tryCatchList(expr, classes, parentenv, handlers)
11. │ └─base (local) tryCatchOne(expr, names, parentenv, handlers[[1L]])
12. │ └─base (local) doTryCatch(return(expr), name, parentenv, handler)
13. ├─jsonlite::toJSON(...)
14. │ └─base::force(x)
15. └─servr (local) build(fromJSON(message))
16. └─sandpaper (local) handler(c(f3, na.omit(f5)))
17. └─sandpaper::build_lesson(f, preview = FALSE, quiet = quiet)
18. └─sandpaper::validate_lesson(path, quiet = quiet)
19. └─lesson$validate_divs()
20. └─purrr::map(...)
21. └─purrr:::map_("list", .x, .f, ..., .progress = .progress)
22. ├─purrr:::with_indexed_errors(...)
23. │ └─base::withCallingHandlers(...)
24. ├─purrr:::call_with_cleanup(...)
25. └─pegboard (local) .f(.x[[i]], ...)
26. └─x$validate_divs(warn = FALSE)
27. └─pegboard:::validate_divs(self)
28. └─pegboard:::make_div_table(yrn)
29. └─yrn$label_divs()
30. └─pegboard:::label_div_tags(self)
31. └─pegboard:::make_div_pairs(nodes, path = path, yaml = yaml)
32. └─pegboard:::raise_div_error(res, path, yaml, type = labels$message)
33. └─base::stop(msg, call. = FALSE)
Oh ho! It turns out that, no matter how much I advocate for not placing arbitrary regulations on what the author can write, I have ended up placing arbitrary regulations on the number of colons for the closing div tags 😮💨.
I've opened carpentries/pegboard#128 to track the issue and I will discuss the solution with @carpentries/workbench-maintainers
I tried to add a long closing fence to an Instructor Note block (following the recommendation we put into the Style guide) and found that pegboard raises an error when a closing fence is more than 80 colons in length. Here's the error output:
Here's the output of
sessionInfo()
:The text was updated successfully, but these errors were encountered: