这是indexloc提供的服务,不要输入任何密码
Skip to content

Conversation

@DanRoscigno
Copy link

@DanRoscigno DanRoscigno commented Jun 6, 2024

With Go < 1.22 I get this error when running the tutorial:

../../go/pkg/mod/github.com/danielgtaylor/huma/v2@v2.18.0/formdata.go:173:21:

undefined: slices.Concat

I think slices.Concat is new in 1.22. With 1.22.4 the tutorial works fine.

I am a tech writer by day, using Go at night to write tests of the docs that I write. I could be completely wrong about the need for 1.22, but here is my reference: https://blog.carlana.net/post/2024/golang-slices-concat/

Summary by CodeRabbit

  • Documentation
    • Updated the required version of Go for Huma from 1.20 to 1.22 in the installation tutorial.

With Go < 1.22 I get this error when running the tutorial:

```
../../go/pkg/mod/github.com/danielgtaylor/huma/v2@v2.18.0/formdata.go:173:21:

undefined: slices.Concat
```
I think slices.Concat is new in 1.22. With 1.22.4 the tutorial works fine.

I am a tech writer by day, using Go at night to write tests of the docs that I write. I could be completely wrong about the need for 1.22, but here is my reference: https://blog.carlana.net/post/2024/golang-slices-concat/
@coderabbitai
Copy link

coderabbitai bot commented Jun 6, 2024

Walkthrough

The recent update to the documentation for Huma's installation tutorial involves changing the required version of Go from 1.20 to 1.22. This ensures that users are informed of the latest necessary version for compatibility and optimal performance.

Changes

Files Change Summary
docs/docs/tutorial/installation.md Updated the required Go version from 1.20 to 1.22

Poem

In the land of code, where versions grow,
Huma's heart now beats with Go.
From one point two-oh, we leap to two-two,
Ensuring our path is fresh and new.
Hop along, dear coder, with cheer and delight,
For with Go 1.22, our future is bright! 🐇✨


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
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 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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @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 as 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 resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.
  • 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.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

Outside diff range and nitpick comments (1)
docs/docs/tutorial/installation.md (1)

Line range hint 13-13: Fix grammar in the installation instructions.

- then go get the Huma dependency to it's ready to be imported:
+ then go get the Huma dependency so it's ready to be imported:

This correction improves the readability and correctness of the installation instructions.

Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 158b076 and 3f548db.

Files selected for processing (1)
  • docs/docs/tutorial/installation.md (1 hunks)
Additional context used
LanguageTool
docs/docs/tutorial/installation.md

[uncategorized] ~13-~13: The preposition ‘as’ seems more likely in this position. (AI_HYDRA_LEO_REPLACE_TO_AS)
Context: ...roject, then go get the Huma dependency to it's ready to be imported: {{ asciinem...

Additional comments not posted (1)
docs/docs/tutorial/installation.md (1)

9-9: Update to Go 1.22 is correctly documented.

This change ensures compatibility with the slices.Concat function introduced in Go 1.22, as mentioned in the PR description.

@danielgtaylor danielgtaylor added the bug Something isn't working label Jun 8, 2024
@danielgtaylor
Copy link
Owner

@DanRoscigno thanks for pointing this out. This is actually a bug as we want to support Go 1.20+. I'll see what to do about this. I know at some point we'll want to move to Go 1.21+ and the slices package was introduced in 1.21.

@SirWaithaka
Copy link

@danielgtaylor in the similar blog post shared by @DanRoscigno, the following is pointed out.

It’s worth noting that if you only want to concatenate two slices, there’s no need to use slices.Concat. You can use the built in append function with the ... spread operator instead:
concat := append(s1, s2...)

Perhaps this is the best approach to fix the bug, similar to https://github.com/danielgtaylor/huma/blame/4a07c36b06f16d507b5f0e18a8a61fc4ed9e8112/formdata.go#L174

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants