fix: use correct target name ExFigCLI for DocC build

[alexey1312]

The package has no target named 'ExFig' — the main target is 'ExFigCLI'.
Updated all DocC build commands and the documentation catalog symbol reference.

https://claude.ai/code/session_01MeeYwatPCABmWk43FpzntD

[gemini-code-assist]

Summary of Changes

Hello @alexey1312, 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 critical misconfiguration in the project's documentation generation process. It ensures that the DocC build system correctly identifies and uses the ExFigCLI target, which is the actual main target, instead of the previously referenced ExFig. This correction enables proper documentation generation and preview, aligning the project's documentation with its codebase.

Highlights

• DocC Target Correction: The pull request fixes an issue where DocC documentation builds were using an incorrect target name, 'ExFig', instead of the correct 'ExFigCLI'.
• Updated Build Commands: DocC generation and preview commands within the mise.toml configuration have been updated to correctly reference the ExFigCLI target.
• Documentation Catalog Update: The main documentation markdown file (ExFig.md) has been updated to reflect the correct ExFigCLI target name in its title.

Changelog

• Sources/ExFigCLI/ExFig.docc/ExFig.md
  • Changed the main title from # ``ExFig`` to # ``ExFigCLI`` to match the correct target name.
• mise.toml
  • Updated the generate-documentation command to use --target ExFigCLI instead of ExFig.
  • Modified the index.html redirect script to point to /documentation/exfigcli.
  • Updated the preview-documentation command to use --target ExFigCLI instead of ExFig.

Ignored Files

• Ignored by pattern: .github/workflows/** (2)
  • .github/workflows/deploy-docc.yml
  • .github/workflows/release.yml

Activity

• The pull request was opened by alexey1312.
• The author referenced a Claude AI session, suggesting AI assistance was used during the development or debugging of this fix.

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 correctly updates the DocC build target from ExFig to ExFigCLI in the documentation catalog and build scripts. The changes are accurate and address the issue described. I have one minor suggestion for the mise.toml file to improve the robustness of the generated documentation's URL paths.

[gemini-code-assist]

The hosting-base-path on line 141 should start with a / to be treated as an absolute path from the host's root (e.g., /ExFig). This makes the generated URLs more robust and aligns with the swift-docc-plugin documentation. I've included this fix along with your change to the target.

    generate-documentation --target ExFigCLI \
    --disable-indexing \
    --transform-for-static-hosting \
    --hosting-base-path /ExFig \