Fix React warning in recent decision summary - #1002
Merged
Merged
Conversation
Contributor
|
Warning Review limit reachedNext included review available in 32 minutes. View limit detailsLimit details: You’ve used the included review currently available. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. Review configuration: ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Team Run ID: 📒 Files selected for processing (1)
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. Comment |
taobojlen
force-pushed
the
fix/investigation-policy-select-value
branch
from
August 12, 2026 03:05
c5debae to
32c1c05
Compare
taobojlen
force-pushed
the
fix/recent-decision-summary-keys
branch
from
August 12, 2026 03:05
8708551 to
38de790
Compare
taobojlen
force-pushed
the
fix/investigation-policy-select-value
branch
from
August 12, 2026 03:42
32c1c05 to
538d54e
Compare
taobojlen
force-pushed
the
fix/recent-decision-summary-keys
branch
from
August 12, 2026 03:42
38de790 to
21e5ce3
Compare
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019fec69-19ab-77e8-b6f0-85af1ed67eed
taobojlen
force-pushed
the
fix/recent-decision-summary-keys
branch
from
August 17, 2026 10:22
21e5ce3 to
5fbfe53
Compare
taobojlen
force-pushed
the
fix/investigation-policy-select-value
branch
from
August 17, 2026 10:22
538d54e to
2da1d55
Compare
taobojlen
changed the base branch from
fix/investigation-policy-select-value
to
main
August 17, 2026 10:23
Co-authored-by: Amp <amp@ampcode.com> Amp-Thread-ID: https://ampcode.com/threads/T-019fec69-19ab-77e8-b6f0-85af1ed67eed
taobojlen
marked this pull request as ready for review
August 18, 2026 13:06
taobojlen
requested review from
cassidyjames,
dom-notion,
juanmrad,
julietshen and
vinaysrao1
as code owners
August 18, 2026 13:06
cassidyjames
enabled auto-merge (squash)
August 31, 2026 22:40
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context & Requests for Reviewers
This fixes a React warning about a missing
key.Tests
Manually tested.
(Optional) Rollout Plan
N/A
Checklist
Only check items that apply to this PR; leave the rest unchecked.
If you changed anything user-facing (i.e. user interface or APIs):
Did you update the CHANGELOG.md and related docs?
If you changed
server/models/**/{ContentTypeModel,ActionModel,RuleModel,PolicyModel}.ts:Did you update the corresponding history tables and their triggers?
If you changed
db/src/scripts/**and usedCREATE TABLE,ADD COLUMN, orALTER COLUMN:Are as many columns marked
NOT NULLas possible? If some columns can sometimes be null depending on other columns, are thereCHECKconstraints capturing those relationships, and are these also reflected using unions in the associated Kysely types?If you added a new signal in
server/services/signalsService/signals/**:Did you classify every error case as a permanent error (
SignalPermanentError, no retry) or a normal error (retryable)? Any case where the signal can't determine a score should be aSignalPermanentError.