fix: replace unwrap with Valid

[emekaokoli19]

/claim #1739

#1739
Fixes #1739 fix: drop unwrap from from_proto

Build & Testing:

• [ x] I ran cargo test successfully.
• [ x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

• I have added relevant unit & integration tests.
• I have updated the documentation accordingly.
• [ x] I have performed a self-review of my code.
• [ x] PR follows the naming convention of <type>(<optional scope>): <title>

Summary by CodeRabbit

• Refactor
  • Improved error handling in data processing with the introduction of a new validation method.
  • Refined error handling and skipping logic in various parts of the code.

[coderabbitai]

Walkthrough

Walkthrough

The update in the from_proto.rs file introduces a new Valid enum for robust error handling and replaces unwrap calls with safer alternatives. This change enhances the reliability and maintainability of the code by using Valid::from_iter for iterable checks and refining error handling throughout the file.

Changes

File	Change Summary
.../from_proto.rs	Introduced Valid enum for error handling, replaced unwrap with safer methods, refined error logic.

Assessment against linked issues

Objective	Addressed	Explanation
Drop unwrap from from_proto (#1739)	✅
Use Valid type in from_proto (#1739)	✅
Implement Valid::from_iter for iterable checks (#1739)	✅

---

Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 67fa7bf and 99402b2.

Files selected for processing (1)

• src/generator/from_proto.rs (7 hunks)

Files skipped from review as they are similar to previous changes (1)

• src/generator/from_proto.rs

---

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 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.

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.
• 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.

[algora-pbc]

💵 To receive payouts, sign up on Algora, link your Github account and connect with Stripe/Alipay.

[amitksingh1490]

actually valid is already defined in valid.rs we need to use that instead of defining a new one

[emekaokoli19]

Sorry for the delay, I have used the Valid in valid.rs

[codecov]

Codecov Report

Attention: Patch coverage is 78.57143% with 12 lines in your changes are missing coverage. Please review.

Project coverage is 86.82%. Comparing base (2c5f9c4) to head (67fa7bf).
Report is 35 commits behind head on main.

❗ Current head 67fa7bf differs from pull request most recent head 99402b2. Consider uploading reports for the commit 99402b2 to get more accurate results

Files	Patch %	Lines
src/generator/from_proto.rs	78.57%	12 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1757      +/-   ##
==========================================
- Coverage   86.93%   86.82%   -0.12%     
==========================================
  Files         155      155              
  Lines       15540    15583      +43     
==========================================
+ Hits        13510    13530      +20     
- Misses       2030     2053      +23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

Action required: PR inactive for 2 days.
Status update or closure in 5 days.

[tusharmath]

Moving to draft until the comments are fixed. Feel free to mark it as read for review whenever you are done fixing the comments.

[tusharmath]

@emekaokoli19 Appreciate your contributions but unfortunately, this PR isn't going in the right direction. Feel free to take help from the contributor's channel on discord and reopen it whenever you are ready.
Thanks once again!