Bugfix/fix template issue

[JamesFreeman]

Fixes #138

[gemini-code-assist]

Summary of Changes

Hello @JamesFreeman, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request resolves a templating issue within the docs/examples.md file, ensuring that code examples, particularly those demonstrating Blade syntax, are rendered correctly. The changes prevent unintended processing by the Liquid templating engine and enhance the presentation of code snippets through specific syntax highlighting directives.

Highlights

• Liquid Templating Control: Added YAML front matter render_with_liquid: false to docs/examples.md to explicitly disable Liquid templating processing for this documentation file.
• Raw Code Block Rendering: Wrapped Blade template code examples within {% raw %} and {% endraw %} tags to ensure they are displayed as literal code and not parsed by any templating engine.
• Improved Syntax Highlighting: Updated the code block language from generic tobladehtml` for the Blade examples, which should provide more accurate syntax highlighting in the documentation.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request aims to fix a template rendering issue in the docs/examples.md file by preventing the Liquid template engine from parsing Blade syntax. The changes introduce a front matter to disable Liquid and also wrap the Blade code example in {% raw %} tags. While this should resolve the rendering problem, the solution introduces some redundancy. I've provided a couple of suggestions to improve the clarity and standardization of the documentation file.

[gemini-code-assist]

The front matter render_with_liquid: false at the top of the file should already prevent Liquid from processing the contents. Therefore, wrapping this block in {% raw %} and {% endraw %} (on line 77) is likely redundant. It's cleaner to rely on the front matter for the entire file. I recommend removing the {% raw %} and {% endraw %} tags.