fix(template): Fix template break line

[yamadashy]

Checklist

• Run npm run test
• Run npm run lint

[bolt-new-by-stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 92.26%. Comparing base (fb2779d) to head (cb15255).
Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #244   +/-   ##
=======================================
  Coverage   92.26%   92.26%           
=======================================
  Files          44       44           
  Lines        2108     2108           
  Branches      462      462           
=======================================
  Hits         1945     1945           
  Misses        163      163           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[coderabbitai]

📝 Walkthrough

Walkthrough

The pull request introduces modifications to several output style templates and the main index file. The changes focus on refining the conditional rendering of template sections in markdown, plain, and XML styles by ensuring proper closing of conditional blocks. In the index file, the export statements are restructured to explicitly re-export the pack function and add a new CliOptions type export, improving the module's export clarity without changing core functionality.

Changes

File	Change Summary
src/core/output/outputStyles/markdownStyle.ts	Adjusted conditional rendering blocks for file summary and directory structure, ensuring proper closing of {{#if}} tags
src/core/output/outputStyles/plainStyle.ts	Modified conditional rendering of file summary and directory structure sections, maintaining correct template structure
src/core/output/outputStyles/xmlStyle.ts	Updated conditional rendering of file_summary and directory_structure XML elements with corrected closing tags
src/index.ts	- Explicitly re-exported pack function from ./core/packager.js - Added export for CliOptions type from ./cli/cliRun.js

Sequence Diagram

sequenceDiagram
    participant Template as Output Template
    participant Flags as Rendering Flags
    
    Flags-->>Template: fileSummaryEnabled
    Flags-->>Template: directoryStructureEnabled
    
    alt When fileSummaryEnabled is true
        Template->>Template: Render File Summary
    end
    
    alt When directoryStructureEnabled is true
        Template->>Template: Render Directory Structure
    end

Loading

The sequence diagram illustrates how rendering flags conditionally control the inclusion of file summary and directory structure sections in the output templates.

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between fb2779d and cb15255.

📒 Files selected for processing (4)

• src/core/output/outputStyles/markdownStyle.ts (1 hunks)
• src/core/output/outputStyles/plainStyle.ts (1 hunks)
• src/core/output/outputStyles/xmlStyle.ts (1 hunks)
• src/index.ts (1 hunks)

🔇 Additional comments (5)

src/index.ts (2)

3-3: Explicit re-export enhances clarity
Re-exporting pack from ./core/packager.js clarifies its origin and use across the codebase. Good move!

---

6-6: Nice addition of CliOptions
Adding CliOptions type export is beneficial for discoverability and helps ensure type safety when passing CLI parameters around.

src/core/output/outputStyles/xmlStyle.ts (1)

40-46: Conditional blocks appear well-structured
Properly closing {{#if}} blocks for fileSummaryEnabled and directoryStructureEnabled ensures the XML template remains well-formed.

src/core/output/outputStyles/plainStyle.ts (1)

45-52: Proper separation of conditional sections
Closing the {{#if fileSummaryEnabled}} block before starting the {{#if directoryStructureEnabled}} block preserves the clarity of the plain text output.

src/core/output/outputStyles/markdownStyle.ts (1)

33-40: Markdown blocks now correctly encapsulated
Ensuring {{#if}} blocks have matching closing tags prevents accidental carry-over of content and maintains proper structure in markdown outputs.

---

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>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• 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 testing code 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

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 using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• 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/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.