Avoiding conflict with reserved keyword type in Rust

[futreall]

Renaming the field from field_type to type in this context causes a conflict with the reserved keyword type in Rust. Using field_type instead of type is the correct solution as it prevents a compilation error and adheres to the language rules.

---

PR-Codex overview

This PR focuses on renaming a field in the LinkBody struct from field_type to type, which likely aligns with a more appropriate naming convention.

Detailed summary

• Changed the field name from field_type to type in the LinkBody struct.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[changeset-bot]

⚠️ No Changeset found

Latest commit: 805ea09

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
hub-monorepo	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 15, 2024 0:19am