docs: add horizontal fill workaround

[fuguiKz]

Issue #619 asks about filling data horizontally (left-to-right) with MiniExcel templates.

MiniExcel template collection rendering currently expands vertically (top-to-bottom), so this PR adds a small doc section (EN + zh-CN) that:

• clarifies the current limitation
• shows a copy/paste workaround by transposing data into a matrix and exporting with MiniExcel.SaveAs(..., printHeader: false)
• mentions an alternative using scalar placeholders for a fixed maximum column count

Refs #619.

[gemini-code-assist]

Summary of Changes

Hello @fuguiKz, 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 addresses a common user need by enhancing the MiniExcel documentation with practical guidance on handling horizontal data filling. It introduces new sections in both English and Chinese README files, offering a primary workaround involving data transposition and an alternative approach using scalar placeholders, thereby improving the clarity and utility of the documentation for users facing this specific challenge.

Highlights

• Horizontal Fill Workaround Documentation: Added a new documentation section in both English and Chinese READMEs detailing workarounds for horizontal data filling with MiniExcel templates.
• Data Transposition Example: Included a C# code example demonstrating how to transpose data into a DataTable for horizontal export when direct template-based horizontal filling is not supported.
• Scalar Placeholder Alternative: Provided an alternative method using scalar placeholders in templates for scenarios requiring styling, noting the need for a fixed maximum column count.
• Clarified Limitations: Explicitly clarified that MiniExcel template collection rendering currently expands vertically (top-to-bottom) and horizontal filling is not yet directly supported.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 adds documentation for a workaround to achieve horizontal data filling, which is a current limitation of MiniExcel templates. The changes are added to both the English and Chinese README files.

My review focuses on improving the provided C# code example. The current example is repetitive and not easily maintainable. I've suggested an alternative using reflection that is more robust and demonstrates a better coding practice for transposing data. This makes the example more useful as a copy-paste solution for users with different data structures.

[gemini-code-assist]

The current example for transposing data is a bit repetitive and not very robust. If properties of the employees objects change, this code would need significant updates.

A more generic approach using reflection would be more resilient to changes and demonstrates a better practice. It automatically discovers the properties and creates a row for each, making the code cleaner and easier to maintain.

Suggested change

	var table = new DataTable();
	table.Columns.Add("A");
	for (var i = 0; i < employees.Length; i++)
	table.Columns.Add($"B{i + 1}");
	table.Rows.Add(new object[] { "Name" }.Concat(employees.Select(e => (object)e.Name)).ToArray());
	table.Rows.Add(new object[] { "Department" }.Concat(employees.Select(e => (object)e.Department)).ToArray());
	table.Rows.Add(new object[] { "City" }.Concat(employees.Select(e => (object)e.City)).ToArray());
	table.Rows.Add(new object[] { "Country" }.Concat(employees.Select(e => (object)e.Country)).ToArray());
	var table = new DataTable();
	table.Columns.Add("Header");
	for (var i = 0; i < employees.Length; i++)
	table.Columns.Add(); // Column names don't matter with printHeader: false
	if (employees.Any())
	{
	var properties = employees.First().GetType().GetProperties();
	foreach (var prop in properties)
	{
	var rowValues = new List<object> { prop.Name };
	rowValues.AddRange(employees.Select(e => prop.GetValue(e)));
	table.Rows.Add(rowValues.ToArray());
	}
	}

[gemini-code-assist]

The current example for transposing data is a bit repetitive and not very robust. If properties of the employees objects change, this code would need significant updates.

A more generic approach using reflection would be more resilient to changes and demonstrates a better practice. It automatically discovers the properties and creates a row for each, making the code cleaner and easier to maintain. This change should be applied to the Chinese documentation as well to maintain consistency with the English version.

Suggested change

	var table = new DataTable();
	table.Columns.Add("A");
	for (var i = 0; i < employees.Length; i++)
	table.Columns.Add($"B{i + 1}");
	table.Rows.Add(new object[] { "Name" }.Concat(employees.Select(e => (object)e.Name)).ToArray());
	table.Rows.Add(new object[] { "Department" }.Concat(employees.Select(e => (object)e.Department)).ToArray());
	table.Rows.Add(new object[] { "City" }.Concat(employees.Select(e => (object)e.City)).ToArray());
	table.Rows.Add(new object[] { "Country" }.Concat(employees.Select(e => (object)e.Country)).ToArray());
	var table = new DataTable();
	table.Columns.Add("Header");
	for (var i = 0; i < employees.Length; i++)
	table.Columns.Add(); // Column names don't matter with printHeader: false
	if (employees.Any())
	{
	var properties = employees.First().GetType().GetProperties();
	foreach (var prop in properties)
	{
	var rowValues = new List<object> { prop.Name };
	rowValues.AddRange(employees.Select(e => prop.GetValue(e)));
	table.Rows.Add(rowValues.ToArray());
	}
	}

[michelebastione]

@fuguiKz Thank you for your contribution! Could you please move your workaround to the FAQ section of the readme and also add it to the README-V2 document?

[fuguiKz]

Thanks @michelebastione! I moved the workaround into the FAQ section of README.md and also added the same FAQ entry to README-V2.md.\n\n(I kept README.zh-CN.md in sync as well—happy to revert that part if you prefer English-only changes.)

[michelebastione]

Looks good, thank you!