Skip to content

Conversation

@aditya-mitra
Copy link
Contributor

@aditya-mitra aditya-mitra commented Dec 16, 2025

Project description activity was blank although changes were made. This PR fixes that behaviour.

before after
image image

Summary by CodeRabbit

  • Enhancements
    • Project activity tracking now records description field changes in addition to name changes, providing more comprehensive visibility into project modifications.

✏️ Tip: You can customize this high-level summary in your review settings.

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Dec 16, 2025

Walkthrough

The EDIT_PROJECT activity configuration in the activity configuration module has been updated to track an additional observable field. The Project entity's monitored properties have been expanded from ['name'] to include both ['name', 'description'].

Changes

Cohort / File(s) Change Summary
Activity Configuration Update
webapp/src/component/activity/configuration.tsx
Updated EDIT_PROJECT activity configuration to track both 'name' and 'description' fields for the Project entity in observable entities specification

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Suggested reviewers

  • JanCizmar

Poem

🐰 A rabbit hops through configs bright,
Where descriptions now catch the light,
Besides the name that once stood tall,
New fields expand—we track them all! ✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely summarizes the main change: enabling display of project description activity and differences, which directly matches the changeset's addition of 'description' to observable entities.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 62f4cea and 8ec77c3.

📒 Files selected for processing (1)
  • webapp/src/component/activity/configuration.tsx (1 hunks)
🧰 Additional context used
📓 Path-based instructions (3)
webapp/**/*.{ts,tsx}

📄 CodeRabbit inference engine (AGENTS.md)

webapp/**/*.{ts,tsx}: Use TypeScript path aliases (tg.component/, tg.service/, tg.hooks/, tg.views/, tg.globalContext/*) instead of relative imports
After backend API changes, regenerate TypeScript types by running npm run schema (and npm run billing-schema if applicable) in the webapp directory
Use typed React Query hooks from useQueryApi.ts for API communication, not raw React Query
Use Tolgee-specific hooks useReportEvent and useReportOnce from 'tg.hooks/useReportEvent' for business event tracking and analytics

Files:

  • webapp/src/component/activity/configuration.tsx
webapp/**/*.tsx

📄 CodeRabbit inference engine (AGENTS.md)

Always use data-cy attributes for E2E test selectors, never rely on text content

Files:

  • webapp/src/component/activity/configuration.tsx
**/*.{ts,tsx,js,jsx,kt,kts}

⚙️ CodeRabbit configuration file

As part of review, please check if the file follows 'The Stepdown Rule': The most important, high-level concepts should be at the top (like a newspaper headline and opening paragraph). Details should increase as you read downward. Functions should be ordered so that a caller appears before the functions it calls. When working with JavaScript components, we allow the main component to live at the bottom of the file as an exception to the rule.

Files:

  • webapp/src/component/activity/configuration.tsx
🔇 Additional comments (1)
webapp/src/component/activity/configuration.tsx (1)

151-151: LGTM! Change correctly enables description tracking.

The addition of 'description' to the tracked fields array follows the established pattern in this configuration file and directly addresses the PR objective. This will now display project description changes in the activity feed.

Please verify that the backend properly emits activity events when the Project description field is modified.


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.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@JanCizmar
Copy link
Contributor

Hey Aditya! Thanks a lot fot all these PRs. I would like to talk o you via DM. Are you open to join our slack workspace https://tolg.ee/slack and send me a DM? ❤️

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