match doesn't seem to work on directories with names starting with .

[vaibhavsagar]

I'm trying to verify my domain for Bluesky, which involves creating a file at <domain>/.well-known/atproto-did. Unfortunately it seems like Hakyll doesn't match correctly on directories starting with .. For example, I would expect code like this:

    match "extra/**" $ do
        route idRoute
        compile copyFileCompiler

To work on files at both extra/regular/foo and extra/.dotted/bar, but it only seems to match on the former while ignoring the latter. I have a small reproducer here. Is this a Hakyll bug or am I doing something wrong?

[chungyc]

If you want to match on files or directories starting with a dot, you have to tell Hakyll not to ignore them.

See:

• ignoreFile in Hakyll.Core.Configuration
• Hakyll.Main.hakyllWith

[vaibhavsagar]

Thanks for pointing that out! I'm not sure that's what's happening here though:

ghci> import Hakyll
ghci> shouldIgnoreFile defaultConfiguration "extras/.well-known/atproto-did"
False
ghci> shouldIgnoreFile defaultConfiguration ".well-known/atproto-did"
False

[vaibhavsagar]

Okay, I updated my configuration with e.g. ignoreFile = const False to test this out and indeed that worked. I'm still confused why shouldIgnoreFile is giving me an inconsistent result but that's a separate issue.

[chungyc]

It checks the name of the file, not the entire path. For example:

λ import Hakyll
λ shouldIgnoreFile defaultConfiguration ".extras"
True
λ shouldIgnoreFile defaultConfiguration ".well-known"
True
λ shouldIgnoreFile defaultConfiguration "well-known/.false"
True
λ shouldIgnoreFile defaultConfiguration ".well-known/false"
False

[vaibhavsagar]

I see, thanks for clarifying!

[jaspervdj]

FWIW I like saving these files without the . in the source of the website so they show up using ls and similar. I then route these to files starting with ..

[vaibhavsagar]

Thanks, that's what I ended up doing too!