diff options
| author | Craig Jennings <c@cjennings.net> | 2026-05-25 08:13:23 -0500 |
|---|---|---|
| committer | Craig Jennings <c@cjennings.net> | 2026-05-25 08:13:23 -0500 |
| commit | 57253375934c98366897a203d7d0a4b8ec96b152 (patch) | |
| tree | a9c3855cab6460e085a933e9980130ccfe424555 /docs/design | |
| parent | cabf4212d6128cf6ff1ed248eb879a68a787627e (diff) | |
| download | dotemacs-57253375934c98366897a203d7d0a4b8ec96b152.tar.gz dotemacs-57253375934c98366897a203d7d0a4b8ec96b152.zip | |
test(elfeed-config): use real structs so tests survive byte-compilation
The cj/elfeed-process-entries tests faked entries as bare symbols and stubbed the elfeed-entry-link accessor, which only works while elfeed-config loads as interpreted source. Byte-compiled, the cl-defstruct accessor inlines to an elfeed-entry-p check plus an aref, so the stub is bypassed and the inlined check rejects the fake entry. Three tests failed the moment a .elc existed.
I rewrote the five process-entries tests to build genuine elfeed-entry structs with elfeed-entry--create, calling package-initialize so the installed elfeed lands on the load-path, and guarded them with skip-unless for an environment that lacks the package. The elfeed-search UI boundary is still stubbed. The four extract-stream-url tests are unchanged.
This unblocks annotating elfeed-config with its load-graph header, which triggers the byte-compile that surfaced the problem.
Diffstat (limited to 'docs/design')
0 files changed, 0 insertions, 0 deletions
