Skip to content

Merge dev to main: Sentry REST formatting + inline checklist serialization#1343

Merged
zbigniewsobiecki merged 5 commits into
mainfrom
dev
May 11, 2026
Merged

Merge dev to main: Sentry REST formatting + inline checklist serialization#1343
zbigniewsobiecki merged 5 commits into
mainfrom
dev

Conversation

@zbigniewsobiecki
Copy link
Copy Markdown
Member

Summary

5 commits since the last dev→main merge:

Test plan

  • dev branch CI green pre-merge
  • Watch main CI + Build and Deploy after merge

🤖 Generated with Claude Code

Cascade Bot and others added 5 commits May 11, 2026 11:48
…oveChecklistItem

addItemToChecklist() anchored insertion at the last checkbox line, so
trailing detail/prose lines that belong to that item got displaced under
the newly-inserted checkbox. Fix: advance insertIdx past non-empty
non-heading lines so the new item always lands after any trailing detail.

removeChecklistItem() called removeSectionBlock with targetLineIdx (the
checkbox line) even when the section held detail lines after the only
checkbox, leaving those lines orphaned before the next heading. Fix:
scanSection now tracks lastContentIdx (last non-empty line in section)
and the single-item deletion path uses it as the section end.

Adds regression tests for both scenarios per reviewer feedback.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…ions

When deleting a checklist item in a multi-item section, also remove any
non-checkbox, non-heading, non-blank detail/prose lines that immediately
follow the deleted checkbox line. Previously only the checkbox line was
spliced out, leaving trailing detail orphaned (e.g. `  Detail for remove`
appearing above the next item or attached to the previous one).

The single-item section path already used `lastContentIdx` to cover this
case; the multi-item `else` branch now scans forward from the target line
and removes the whole item block in a single splice.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…-checklist-locks

fix(pm): serialize inline checklist description updates
* fix(sentry): handle REST issue event formatting

* fix(sentry): handle REST request query as tuple pairs, record, or string

Widens SentryRequest with a `query` field (tuple pairs | record | string)
to cover Sentry's Retrieve-an-Issue-Event REST shape where query params
are returned under `data.query` rather than `queryString`. Adds
normalizeRequestQuery() helper that falls back from query_string/queryString
to the tuple-pairs/record/string shape, and regression tests for each
variant plus the precedence rule.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

---------

Co-authored-by: Cascade Bot <bot@cascade.dev>
Co-authored-by: Claude Sonnet 4.6 <noreply@anthropic.com>
@zbigniewsobiecki zbigniewsobiecki merged commit e6d6582 into main May 11, 2026
14 checks passed
@codecov
Copy link
Copy Markdown

codecov Bot commented May 11, 2026

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.

2 participants