fix: set default false for statObject's deletemarker

[jiuker]

fix: set default false for statObject's deletemarker
fix #195

can be read to true for Undefined Behavior

[coderabbitai]

📝 Walkthrough

Walkthrough

The response types now initialize delete_marker to false. The StatObject() test verifies that retrieved objects are not marked for deletion.

Changes

Delete marker defaults

Layer / File(s)	Summary
Response defaults and StatObject() validation include/miniocpp/response.h, tests/tests.cc	StatObjectResponse::delete_marker and DeletedObject::delete_marker now default to false. The StatObject() test fails when delete_marker is true.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Suggested reviewers: harshavardhana

Poem

I’m a rabbit with a marker set right,
False by default, clean and bright.
The object test checks the state,
No phantom delete shall pass the gate.
Hop, hop—safe responses take flight!

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Linked Issues check	✅ Passed	The changes set StatObjectResponse.delete_marker to false and verify that existing objects are not delete markers [#195].
Out of Scope Changes check	✅ Passed	The changes are limited to related delete-marker defaults and validation for StatObject behavior.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly describes the main change: setting the delete_marker default to false for StatObjectResponse.

---

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