Skip to content

Applied rules for tool messages #6263

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

RomneyDa
Copy link
Collaborator

Rearranges our messaging thunks a bit so that construct messages is only called in one place and applied rules are added to tool messages as well

@RomneyDa RomneyDa requested a review from a team as a code owner June 23, 2025 17:51
@RomneyDa RomneyDa requested review from sestinj and removed request for a team June 23, 2025 17:51
Copy link

netlify bot commented Jun 23, 2025

Deploy Preview for continuedev canceled.

Name Link
🔨 Latest commit 15b4f4c
🔍 Latest deploy log https://app.netlify.com/projects/continuedev/deploys/685b16a236f15b0008349bb7

@dosubot dosubot bot added the size:L This PR changes 100-499 lines, ignoring generated files. label Jun 23, 2025
Copy link

recurseml bot commented Jun 23, 2025

⚠️ Only 5 files will be analyzed due to processing limits.

Copy link

recurseml bot commented Jun 23, 2025

✨ No issues found! Your code is sparkling clean! ✨

Copy link
Contributor

@sestinj sestinj left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think that we should start now with writing tests that cover the thunk logic. Probably vitest "integration" tests would be better than a unit test of all the individual thunks. Kent D. Dodds (seems important) seems to agree: https://redux.js.org/usage/writing-tests#guiding-principles

But just something that checks the state before / after is what seems important

Would be fine if the tests are light for now, but at least get to POC where we are comfortable writing more of them in the future

@github-project-automation github-project-automation bot moved this from Todo to In Progress in Issues and PRs Jun 24, 2025
@RomneyDa RomneyDa marked this pull request as draft June 30, 2025 17:45
@RomneyDa RomneyDa closed this Jun 30, 2025
@github-project-automation github-project-automation bot moved this from In Progress to Done in Issues and PRs Jun 30, 2025
@github-actions github-actions bot locked and limited conversation to collaborators Jun 30, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
size:L This PR changes 100-499 lines, ignoring generated files.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

2 participants