Skip to content

Conversation

@Mini256
Copy link
Member

@Mini256 Mini256 commented May 7, 2025

part of #664

  • llamaindex already supports rendering prompt templates via the jinja2 rendering engine through RichPromptTemplate, so we don't need to get_prompt_by_jinja2_template.
  • We no longer need placeholders like <<query_str>> to avoid escaping, and can define prompt template variable placeholders uniformly using the {{xxx}} syntax. (breaking change)

@vercel
Copy link

vercel bot commented May 7, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
autoflow ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 7, 2025 1:37pm
2 Skipped Deployments
Name Status Preview Comments Updated (UTC)
tidb-ai-preview ⬜️ Ignored (Inspect) May 7, 2025 1:37pm
tidb-ai-storybook ⬜️ Ignored (Inspect) May 7, 2025 1:37pm

@Mini256 Mini256 changed the title refactor: (breaking change) using RichPromptTemplate instead of get_prompt_by_jinja2_template method refactor: (breaking change) using RichPromptTemplate instead of get_prompt_by_jinja2_template function May 7, 2025
@Mini256 Mini256 merged commit d304352 into main May 7, 2025
10 checks passed
@Mini256 Mini256 deleted the feat-using-rich-prompt-template branch May 7, 2025 13:53
NG85 pushed a commit to NG85/autoflow that referenced this pull request May 9, 2025
…rompt_by_jinja2_template function (pingcap#680)

part of pingcap#664

- llamaindex already supports rendering prompt templates via the jinja2
rendering engine through `RichPromptTemplate`, so we don't need to
`get_prompt_by_jinja2_template`.
- We no longer need placeholders like <<query_str>> to avoid escaping,
and can define prompt template variable placeholders uniformly using the
{{xxx}} syntax. (breaking change)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants