Skip to content

fix: omit empty Bluesky reply field#21

Open
vivanvv wants to merge 1 commit into
ricardodantas:mainfrom
vivanvv:fix/bluesky-empty-reply
Open

fix: omit empty Bluesky reply field#21
vivanvv wants to merge 1 commit into
ricardodantas:mainfrom
vivanvv:fix/bluesky-empty-reply

Conversation

@vivanvv

@vivanvv vivanvv commented Jun 8, 2026

Copy link
Copy Markdown

Summary

  • Omit the Bluesky reply field from post records when there is no reply reference
  • Add a regression test covering the com.atproto.repo.createRecord payload shape

Fixes #4.

Testing

  • cargo fmt --check
  • cargo test --locked
  • cargo clippy --all-targets

I did not test by live-posting to Bluesky. The regression test covers the rejected payload shape by checking that normal posts no longer serialise reply: None as "reply": null.

@changeset-bot

changeset-bot Bot commented Jun 8, 2026

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: b1e1b34

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Error message "Record/reply must be an object" when posting to Bluesky

1 participant