While working on #32, I found sequoia inject was skipping all files. Stepping through the code (after enabling source maps with bun, which ignores the tsconfig.json setting - I'll submit a separate PR), I found it's because of how the slugToAtUri dictionary is created as well as how files are resolved. Honestly, it'll be hard to unwind the template so maybe we should build up the slugToAtUri - maybe even cache additional fields in .sequoia-state.json - to contain more information so we can have a step apply the template and try a match.
Or, maybe this is just something we need to document on the site: that if you're using advanced features like pathTemplate, you - the site author - need to make sure you emit <link> tags in the <head> yourself for the document and publication URIs. Might be a good idea anyway even if inject adds support just for a "manual setup" doc.
Hmm, my initial gut reaction is to do the latter and update the docs.
injectis a bit of a hack and a bold one at that 😅It's much more stable to work with the framework you're using to populate those tags. If we do try to solve this I say we do it in a separate PR from the one solving #32.I would also be curious to see how many people might be using
injectin their workflows. Admittedly I think our docs could give more concrete examples of how you can use your SSG to help populate these tags.