✨ Add encoded entry data reader

[ChanTsune]

No description provided.

[coderabbitai]

Warning

Review limit reached

@ChanTsune, we couldn't start this review because you've used your available PR reviews for now.

Your plan currently allows 1 review/hour. Refill in 27 minutes and 10 seconds.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more review capacity refills, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than trial, open-source, and free plans. In all cases, review capacity refills continuously over time.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: d3848151-5eb6-4c4f-bde6-7b34c864ddd4

📥 Commits

Reviewing files that changed from the base of the PR and between 82b7983 and 854e837.

📒 Files selected for processing (1)

• lib/src/entry.rs

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch api/encoded-data-reader

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[gemini-code-assist]

Code Review

This pull request introduces the EncodedDataReader struct to provide a unified way to read raw, encoded entry data from FDAT and SDAT chunks before decryption or decompression. Both NormalEntry and SolidEntry now expose an encoded_reader() method, and internal components like EntryDataReader and EntryIterator have been refactored to utilize this new reader, simplifying type signatures and reducing code duplication. Additionally, unit tests were added to verify the correct behavior of the encoded readers for both entry types. I have no feedback to provide as there were no review comments.