fix: add scoped error logging for lexer/parser errors
- Add std.log.scoped(.pugz) to template.zig and view_engine.zig - Log detailed error info (code, line, column, message) when parsing fails - Log template path context in ViewEngine on parse errors - Remove debug print from lexer, use proper scoped logging instead - Move benchmarks, docs, examples, playground, tests out of src/ to project root - Update build.zig and documentation paths accordingly - Bump version to 0.3.1
This commit is contained in:
36
playground/examples/text.pug
Normal file
36
playground/examples/text.pug
Normal file
@@ -0,0 +1,36 @@
|
||||
| An example of an
|
||||
a(href='#') inline
|
||||
| link.
|
||||
|
||||
form
|
||||
label Username:
|
||||
input(type='text', name='user[name]')
|
||||
p
|
||||
| Just an example of some text usage.
|
||||
| You can have <em>inline</em> html,
|
||||
| as well as
|
||||
strong tags
|
||||
| .
|
||||
|
||||
| Interpolation is also supported. The
|
||||
| username is currently "#{name}".
|
||||
|
||||
label Email:
|
||||
input(type='text', name='user[email]')
|
||||
p
|
||||
| Email is currently
|
||||
em= email
|
||||
| .
|
||||
|
||||
// alternatively, if we plan on having only
|
||||
// text or inline-html, we can use a trailing
|
||||
// "." to let pug know we want to omit pipes
|
||||
|
||||
label Username:
|
||||
input(type='text')
|
||||
p.
|
||||
Just an example, like before
|
||||
however now we can omit those
|
||||
annoying pipes!.
|
||||
|
||||
Wahoo.
|
||||
Reference in New Issue
Block a user