feat: support comfort spaces in code block meta

data/notes/Keep Kalm, Rust.md

@@ -10,7 +10,7 @@ I have to admit, I was quite excited getting to that part when I started [[notes
 So when do you panic in Rust? Well, just like in real life, you do when something happens and you cannot do anything about it.
 
 Put more precisely, panicking is what you do when you encounter an unrecoverable error in Rust. As it's a thread-based mechanism, I assume it kills it in some way(?) while other threads can carry around their work, handling the panicked thread if needed.
-```rust[src/main.rs]
+```rust [src/main.rs]
 fn main() {
 	if (something_bad) {
 		panic!();

data/notes/Let's Get Coding With Rust.md

@@ -14,7 +14,7 @@ Indeed, learning how to write it only gets you so far, at one point you also nee
 This starts with code organization.
 
 Contrary to JavaScript, Rust doesn't have an `import`/`export` system so to say because you don't import files. Instead Rust has "modules", which reminds me vaguely of PHP namespaces (for which I have a *vague* and *distant* memory of) and C includes.
-```rust[src/greetings/mod.rs]
+```rust [src/greetings/mod.rs]
 // `greetings` module root, `mod.rs` is recognized as such
 
 // `hello` is a public function of the `greetings` module
@@ -24,7 +24,7 @@ pub fn hello() {
 ```
 
 You cannot *import* modules, instead you have to *reference* them, which you can if they are exposed to the file you're working on.
-```rust[src/main.rs]
+```rust [src/main.rs]
 mod greetings; // reference of the `greetings` module
 
 fn main() {

data/notes/Rust Workspaces.md

@@ -10,11 +10,11 @@ I'm not sure yet if this comes as a result of great design and thoughtful archit
 Anyway. Today I've learned about Rust built-in workspace support. Similarly to [npm's workspaces](https://docs.npmjs.com/cli/v7/using-npm/workspaces), they allow you to develop multiple packages within the same codebase, i.e. developing within a monorepo.
 
 To leverage them, we just need to create a directory featuring a root `Cargo.toml` declaring our workspace.
-```toml[Cargo.toml]
+```toml [Cargo.toml]
 [workspace]
 members = [
-	"src",
-	"examples/hello-world"
+  "src",
+  "examples/hello-world"
 ]
 ```
 

src/akte/lib/highlightCode.ts

@@ -95,9 +95,9 @@ function parseLineHighlightsString(raw: string): number[][] {
 export function parseMarkdownCodeBlock(markdownCodeBlock: string): ParseMarkdownCodeBlockReturnType {
 	const maybeMatch = markdownCodeBlock.match(
 		/**
-		 * @see https://regex101.com/r/gzGiA5/1
+		 * @see https://regex101.com/r/gzGiA5/3
 		 */
-		/^\s*\/(?<language>[\w-]+)?(?:\[(?<filename>[/\w\s.~-]*)\])?(?:\{(?<lineHighlightsString>[\s\d,-]*)\})?\/(?<code>[\s\S]*)/,
+		/^\s*\/(?<language>[\w-]+)?\s?(?:\[(?<filename>[/\w\s.~-]*)\])?(?:\{(?<lineHighlightsString>[\s\d,-]*)\})?\s?\/(?<code>[\s\S]*)/,
 	)
 
 	if (!maybeMatch || !maybeMatch.groups) {

src/akte/lib/markdownToHTML.ts

@@ -30,7 +30,7 @@ const remarkHighlightCode: Plugin<[], MDRoot> = () => {
 			parent: MDParent,
 		): Promise<void> => {
 			const value = await highlightCode(
-				parseMarkdownCodeBlock(`/${node.lang}/\n${node.value}`),
+				parseMarkdownCodeBlock(`/${node.lang} ${node.meta || ""}/\n${node.value}`),
 			)
 
 			parent.children.splice(index, 1, { type: "html", value })