Fix null data handling in Write_File_To_Path method

[T-rav]

This pull request addresses a potential bug in the Write_File_To_Path method of the FileSystem.cs file. The method now includes a check to ensure that the file.Data is not null before attempting to write to the file. If file.Data is null, an error message is added to the result.ErrorMessages, and the method returns early, preventing any further execution that could lead to exceptions. This change improves the robustness of the file writing process.

---

This pull request was co-created with Cosine Genie

Original Task: DotnetCore-FileSystem/s7xlwblohrt1
Author: Travis Frisinger

Summary by CodeRabbit

• Bug Fixes
  • Improved file writing reliability by preventing attempts to write files with missing data and displaying a clear error message when no file data is provided.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

A validation step was added to the Write_File_To_Path method to check if the file.Data property is null. If so, an error is recorded and the method returns early, preventing attempts to write when no file data is present. A new asynchronous test was added to verify this behavior. No public interfaces or method signatures were changed.

Changes

File(s)	Change Summary
source/StoneAge.Data.FileSystem/FileSystem.cs	Added null check for file.Data in Write_File_To_Path; returns error if data is missing
source/StoneAge.Data.FileSystem.Tests/FileSystemTests.cs	Added async test WhenFileDataIsNull_ExpectErrorMessage to verify error returned when file data is null

Poem

A bunny hopped to check the file,
“Is there data?”—paused a while.
If none is found, it will not write,
Just leaves an error, skips the fight.
With careful code, the bugs take flight,
And files are safe all through the night! 🐇✨

---

📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 13a7ac4 and 339d6c3.

📒 Files selected for processing (1)

• source/StoneAge.Data.FileSystem.Tests/FileSystemTests.cs (2 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

---

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

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

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 75b0a16 and 13a7ac4.

📒 Files selected for processing (2)

• source/StoneAge.Data.FileSystem.Tests/FileSystemTests.cs (1 hunks)
• source/StoneAge.Data.FileSystem/FileSystem.cs (2 hunks)

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

• source/StoneAge.Data.FileSystem/FileSystem.cs

🧰 Additional context used

🪛 GitHub Check: build

source/StoneAge.Data.FileSystem.Tests/FileSystemTests.cs

[failure] 124-124:
'IDocumentBuilderData' does not contain a definition for 'Create_Document' and no accessible extension method 'Create_Document' accepting a first argument of type 'IDocumentBuilderData' could be found (are you missing a using directive or an assembly reference?)

---

[failure] 124-124:
'IDocumentBuilderData' does not contain a definition for 'Create_Document' and no accessible extension method 'Create_Document' accepting a first argument of type 'IDocumentBuilderData' could be found (are you missing a using directive or an assembly reference?)

🪛 GitHub Actions: .NET

source/StoneAge.Data.FileSystem.Tests/FileSystemTests.cs

[error] 124-124: CS1061: 'IDocumentBuilderData' does not contain a definition for 'Create_Document' and no accessible extension method 'Create_Document' accepting a first argument of type 'IDocumentBuilderData' could be found (are you missing a using directive or an assembly reference?)