docs(logic): fix missing language for fenced code

[ccamel]

Fix the absence of a language spec in the fenced code block for the "program" section of the feature scenario. This adjustment is needed to satisfy the requirements of the okp4/docs linter, cf error reported:

predicates/bech32_address_2.md:138 MD040/fenced-code-language Fenced code blocks should have a language specified [Context: "```"]

Summary by CodeRabbit

• Documentation
  • Improved clarity in documentation by adding language hints to code blocks.
• New Features
  • Enhanced interpretation of program blocks in scenarios by adding specific language tags.

[coderabbitai]

Walkthrough

The recent updates involve enhancing documentation and code to improve clarity and functionality. Specifically, changes were made to include prolog language hints in documentation and feature files, ensuring proper interpretation and readability of code blocks. Additionally, a modification in a Go template adjusts the default media type, optimizing the scenario's execution context.

Changes

File Path	Change Summary
docs/predicate/.../bech32_address_2.md x/logic/keeper/features/.../bech32_address_2.feature	Added prolog language hint to code blocks.
scripts/templates/func.go.txt	Modified default media type in code snippet.

🐇

In the land of code, where logic plays,
A rabbit hopped through document maze.
With prolog hints and types anew,
It tweaked the scripts, as through they flew.
🌟 "To clarity and beyond!" it cheered,
Ensuring that no bug neared.
🎉 A hop, a skip, in digital grace,
Celebrating changes, in the codebase space.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit-tests for this file.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository from git and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 09cfc04 and c922298.

Files selected for processing (3)

• docs/predicate/bech32_address_2.md (1 hunks)
• scripts/templates/func.go.txt (1 hunks)
• x/logic/keeper/features/bech32_address_2.feature (2 hunks)

Files skipped from review due to trivial changes (2)

• docs/predicate/bech32_address_2.md
• scripts/templates/func.go.txt

Additional comments: 2

x/logic/keeper/features/bech32_address_2.feature (2)

• 89-89: The addition of the prolog tag before the program block is a good practice for clarity and readability. It helps in correctly interpreting the code block's language, which is essential for syntax highlighting in documentation or IDEs.
• 107-107: Similarly, the inclusion of the prolog tag here is consistent with best practices for documenting code blocks in markdown files. This ensures that the code is properly interpreted and displayed, enhancing the documentation's overall quality.

[bot-anik]

🎉 This PR is included in version 7.0.1 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀