The tldr; is that in my situation, for this particular part of my code, I
have to halt my Pollen server, reset the cache, and restart the server for
any changes to be visible. This is necessary, despite having disabled
Pollen's caching. Here's the context:
- I have disabled caching in my root pollen.rkt file like so:
- (module setup racket/base
(provide (all-defined-out))
(define poly-targets '(html))
(define compile-cache-active #f)
(define render-cache-active #f))
- It is unclear to me if I need to repeat this declaration in each
subsequent pollen.rkt in each subdirectory. Whether I do or not, seems to
have no effect on this problem, or anything else.
- A very brief explanation of my book for context for this question:
the book I am working on is a translation of the I Ching which, long story
short, centers around 64 hexagrams that look like ䷂ or ䷄ or ䷆ and so on
(there are 64 of them). I needed a way to construct these hexagrams while
retaining control of the individual lines (rather than simply using the
unicode character, I will be building the hexagram out of <span>s
containing ⚋ and ⚊ (yin and yang) unicode characters (this is so that I can
enable mouse-over highlighting).
- Thus, I have a data structure that looks like this:
- (define (hexagrams) #hash(
(1 . ('yang 'yang 'yang 'yang 'yang 'yang))
(2 . ('yin 'yin 'yin 'yin 'yin 'yin))
(3 . ('yang 'yin 'yin 'yin 'yang 'yin))
(4 . ('yin 'yang 'yin 'yin 'yin 'yang))
- I refer to each of the values in the corresponding lists as
"poles". I have the following function:
- (define (->monogram pole)
(case pole
[''yang (monogram (yang))]
[else (monogram (yin))]))
- "monogram" returns a txexpr, and "yang" and "yin" both return
unicode strings. So the result of calling (->monogram 'yin) yields
<span>⚋</span>
- I'm not sure if this is related, but in this book, each hexagram
represents a chapter and thus has its own file. For instance, Hexagram 1
lives in hexagrams/1.poly.pm, 2 lives in hexagrams/2.poly.pm, and so on.
I
wrote a function that takes the current document's filename and splits
the
path apart until I have the current hexagram number. I then use that
number
to look up the corresponding list from the *hexagrams* immutable hash
(shown in the first code block). This provides some
automation/centralization for an otherwise error-prone process of
transcribing this book.
The problem is, when I may *any* changes to these functions, I have to halt
my Pollen server, reset the cache, and restart the server for any changes
to appear. I experience frequent caching problems across the board (despite
disabling Pollen cache), but they are heisenbug-esque. This is the only
case that is reproducible for me on a consistent basis.
--
You received this message because you are subscribed to the Google Groups
"Pollen" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.