[feature request] Specify per-collection remark/rehype transforms

[vadimkantorov]

IIUC the remark/rehype transforms can only be specified globally, but it would be very useful to specify some transforms only for some collections or configure them differently depending on collection

Are there any workarounds for the time being?

[delucis]

You can check the path of the current file from a plugin to decide whether to process it or not as a workaround:

function remarkPlugin() {
	return function attacher() {
		return function transformer(tree, file) {
			if (!shouldTransformFile(file)) {
				return;
			}

			// manipulate things
		};
	};
}

The file parameter has a path property you can use in this case.

[vadimkantorov]

I'm currently having a custom glob loader and overriding parseData to inject extra frontmatter values before schema validation. How could I pass down some per-entry values from glob loader to be accessible in remark plugin?

Currently extra frontmatter values injected in parseData reach schema validation and Astro rendering, but do not reach remark plugin / file.data.astro.frontmatter object

Do I need to also override load? Could you please suggest an example?

Basically I'd like to propagate down a string value to store the name of collection

[delucis]

Good question — it’s not something I’ve had to do before. But yes, I think you’re right that you’d need to use load() if you want to alter the actual content that will be loaded.

[vadimkantorov]

I'm wanting to alter frontmatter / metadata so that it can be accessible to a remark plugin downstream (so that I could pass down the collection name)