replace interface{} with "any"

[noborus]

Summary by CodeRabbit

• Refactor
  • Enhanced data handling in reading and writing functions to support a broader range of input types.

[coderabbitai]

Walkthrough

The changes across the files indicate a shift from using interface{} to any for variable types in Go code, reflecting a language update for type parameters. The TestXLSXReader_PreReadRow and TestXLSXWriter_WriteRow functions in tests, along with the WriteRow function in the XLSXWriter type, now use any to handle a broader and more flexible range of types.

Changes

File Path	Change Summary
.../reader_test.go	Updated want variable type from [][]interface{} to [][]any.
writer.go	Changed WriteRow parameter type from []interface{} to []any.
.../writer_test.go	Modified row parameter type from []interface{} to []any in tests.

Poem

🐇 CodeRabbit hopped along, 🛠️ fixing types with a song,
From interface{} to any, the code now strong,
A leap in types, where they belong,
In the land of Go, we code on! 🎶

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 44caec1 and c18518c.

Files ignored due to filter (2)

• go.mod
• go.sum

Files selected for processing (3)

• reader_test.go (3 hunks)
• writer.go (1 hunks)
• writer_test.go (3 hunks)

Additional comments: 8

writer_test.go (3)

• 18-18: The change from []interface{} to []any is consistent with the PR objectives and the evolution of Go's type system.

• 38-38: The use of []any in test case arguments is correctly implemented and matches the updated function signature.

• 57-57: The update to []any for the row slice in the second test case is also correct and consistent with the rest of the changes.

reader_test.go (4)

• 75-75: The update to [][]any for the want variable in the test cases is in line with the PR's goal to modernize the codebase using Go's latest features.

• 83-83: The change to [][]any is correctly applied in the first test case.

• 101-101: The use of [][]any in the second test case is consistent with the changes made in the first test case and aligns with the updated type system in Go.

• 116-116: The third test case also correctly reflects the change to [][]any, ensuring consistency across all test cases.

writer.go (1)

• 213-213: The modification of the WriteRow function to accept a slice of any is consistent with the PR's objectives and the modernization of the Go codebase.