sozo(unrealengine): handle UE5.6 and Dojo 1.5

[caillef]

This PR fixes the generated files using sozo build --unrealengine.

• std::vector are not working anymore in UE5.6, we must use TArray
• Handle the new pagination system (not implemented yet but at least it compiles and fetch the latest 1000 entities)

Summary by CodeRabbit

• Bug Fixes
  • Improved compatibility with Unreal Engine by updating how string collections are handled in asynchronous functions.
  • Enhanced entity fetching by switching to a paginated approach for better data management and reliability.

[coderabbitai]

Walkthrough

Ohayo sensei! This update refactors internal logic in the Unreal Engine plugin by replacing std::vector<std::string> with Unreal's TArray<std::string>, updates entity fetching to use a paginated API, and adjusts error handling and data access accordingly. No changes were made to public or exported entity declarations.

Changes

File(s)	Change Summary
crates/dojo/bindgen/src/plugins/unrealengine/...	Switched from std::vector<std::string> to TArray<std::string>, updated entity fetch API usage, and revised error/data handling in async functions.

Suggested reviewers

• kariy
• glihm

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 79963e2 and 62eb3e7.

📒 Files selected for processing (1)

• crates/dojo/bindgen/src/plugins/unrealengine/mod.rs (3 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (1)

• GitHub Check: fmt

🔇 Additional comments (3)

crates/dojo/bindgen/src/plugins/unrealengine/mod.rs (3)

1238-1238: Ohayo sensei! LGTM - Perfect UE5.6 compatibility fix!

The replacement of std::vector<std::string> with TArray<std::string> and corresponding push_back to Add method change is exactly what's needed for UE5.6 compatibility. This aligns perfectly with the PR objectives.

Also applies to: 1244-1244

---

1257-1257: Consistent application of UE5.6 fix - nice work sensei!

Same container type migration applied consistently to ExecuteFromOutside function. The uniform application of these changes across both execution functions ensures compatibility.

Also applies to: 1263-1263

---

1274-1288: Ohayo! Solid pagination implementation for Dojo 1.5 sensei!

The migration to ResultPageEntity with paginated data access (&resEntities.ok.items) correctly implements the new Dojo 1.5 API. The hardcoded 1000 entity limit aligns with the PR's preliminary pagination support goals.

The error handling updates (ErrPageEntity tag) and cleaner async lambda formatting are well-executed improvements.

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate Unit Tests

• Create PR with Unit Tests
• Post Copyable Unit Tests in Comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ 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>, please review it.
  • Explain this complex logic.
  • 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 explain this code block.
  • @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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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 using 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 generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai auto-generate unit tests to generate unit tests for this 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.