From 021d5f989ae41ae39a9b937b498141d9dc70d894 Mon Sep 17 00:00:00 2001
From: Titus Wormer <tituswormer@gmail.com>
Date: Thu, 9 Jun 2022 15:01:46 +0200
Subject: Add basic subtokenization, string content in fenced code

---
 src/parser.rs | 12 ++++++++++--
 1 file changed, 10 insertions(+), 2 deletions(-)

(limited to 'src/parser.rs')

diff --git a/src/parser.rs b/src/parser.rs
index e156e33..5648942 100644
--- a/src/parser.rs
+++ b/src/parser.rs
@@ -2,13 +2,21 @@
 // To do: this should start with `containers`, when they’re done.
 // To do: definitions and such will mean more data has to be passed around.
 use crate::content::flow::flow;
-use crate::tokenizer::{as_codes, Code, Event};
+use crate::tokenizer::{as_codes, Code, Event, Point};
 
 /// Turn a string of markdown into events.
 /// Passes the codes back so the compiler can access the source.
 pub fn parse(value: &str) -> (Vec<Event>, Vec<Code>) {
     let codes = as_codes(value);
     // To do: pass a reference to this around, and slices in the (back)feeding. Might be tough.
-    let events = flow(&codes);
+    let events = flow(
+        &codes,
+        Point {
+            line: 1,
+            column: 1,
+            offset: 0,
+        },
+        0,
+    );
     (events, codes)
 }
-- 
cgit