Skip to content

Conversation

randall-vx
Copy link
Contributor

Error handling in both TaskComment and TaskInfo is now improved

  • Add more specific error messages (e.g., include context like "Failed to update comment" or "Failed to assign user").
  • Log errors to the console for debugging.
  • Ensure all errors are surfaced to the user (no silent failures).
  • Errors are logged to the console for easier debugging.
  • Silent failures are avoided; users always get actionable feedback.

package.json Outdated
Comment on lines 25 to 26
"version": "1.2.4",
"dependencies": {
"@types/react": "^19.1.11",
"@types/react-dom": "^19.1.7",
"react": "^19.1.1",
"react-dom": "^19.1.1"
}
Copy link
Member

Choose a reason for hiding this comment

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

No need for these dependencies in the root folder as they are used in the apps/web and they're present there. Also I see a package-lock, we don't need that as we use pnpm. Other than that it looks good!

@randall-vx randall-vx force-pushed the main-dev-issue-2 branch 2 times, most recently from 3a92360 to 420da89 Compare September 18, 2025 20:46
Error handling in both TaskComment and TaskInfo is now improved

- Add more specific error messages (e.g., include context like "Failed to update comment" or "Failed to assign user").
- Log errors to the console for debugging.
- Ensure all errors are surfaced to the user (no silent failures).
- Errors are logged to the console for easier debugging.
- Silent failures are avoided; users always get actionable feedback.
@randall-vx
Copy link
Contributor Author

randall-vx commented Oct 2, 2025

Hi @aacevski any news on this PR ?

regards,

@aacevski
Copy link
Member

aacevski commented Oct 8, 2025

Hey @randall-vx - thank you so much for contributing. I see the changes for the email are included here as well, as I mentioned in that ticket - I've been focused on the v2 branch and added some of these changes. Do you think it makes sense to re-open the PR pointed towards that branch?

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