I've pushed changes so that the set of module suffixes is extensible
through a `module-suffixes` definition in a collection's info.rkt.
Adding a new suffix affects compilation and testing in all collections.
(The suffixes .rkt, .scrbl, .ss, and .scm remain hard-wired
in the set.)
Module suffixes
The docs for `compile-collection-zos` [1] say that all files with the
extension .rkt, .ss, or .scm in a collection are compiled and that
within info.rkt, one can specify paths to omit with `compile-omit-paths`.
Is there way to go the opposite direction — specify *extra* files that should
be
I've been bumping into variants of this problem — namely, difficulty using
special source extensions — across the Racket ecosystem. In addition to
this one,
[2] Adding file types to `raco test`
[3] Persuading DrRacket to handle special source-file extensions
Is the underlying problem that I'm
It looks like there's not a way currently, although I think it would
make sense to add one.
For file extensions generally, I think there should be an info.rkt
field to add extensions that are recognized by all tools that apply to
all collections. That's a larger project, but it's on my near-term
No, not as long as you're willing to push the envelope here.
Goes without saying.
FWIW the Pollen file extensions are not purely cosmetic. The Pollen renderer
consumes Pollen source files and uses the extension (pm, pmd, pp, etc) to
determine what kind of rendering is necessary. Of course
5 matches
Mail list logo
