enigma145618
01/02/2026, 8:39 PM@description(r#"foobar"#) for a field in a class no longer allowed as of BAML >=0.215.0? This was working in <=0.214.0.aaronv (BAML)
01/02/2026, 8:40 PMaaronv (BAML)
01/02/2026, 8:40 PMaaronv (BAML)
01/02/2026, 8:40 PM// This is a BAML config file, which extends the Jinja2 templating language to write LLM functions.
class Resume {
name string
education Education[] @description("Extract in the same order listed")
skills string[] @description(#"Only include programming language
sefsefsefserwercwerwer
s"#)
}
class Education {
school string
degree string
year int
}
function ExtractResume(resume_text: string) -> Resume {
// see clients.baml
client GPT4o
// The prompt uses Jinja syntax. Change the models or this text and watch the prompt preview change!
prompt #"
Parse the following resume and return a structured representation of the data in the schema below.
Resume:
---
{{ resume_text }}
---
{# special macro to print the output instructions. #}
{{ ctx.output_format }}
JSON:
"#
}
test Test1 {
functions [ExtractResume]
args {
resume_text #"
John Doe
Education
- University of California, Berkeley
- B.S. in Computer Science
- 2020
Skills
- Python
- Java
- C++
"#
}
}aaronv (BAML)
01/02/2026, 8:40 PMrenigma145618
01/02/2026, 8:41 PMr. I was seeing this on my end.enigma145618
01/02/2026, 8:41 PMr.aaronv (BAML)
01/02/2026, 8:42 PMr somewhere?enigma145618
01/02/2026, 8:42 PMr is working now.enigma145618
01/02/2026, 8:42 PMr# strings.aaronv (BAML)
01/02/2026, 8:42 PMenigma145618
01/02/2026, 8:42 PM