chore: FeatureFlag add createdAt and updatedAt

[matt-aitken]

It’s useful to know when they were modified for debugging and auditing.

For existing rows createdAt and updatedAt are set to now() during the migration, to avoid a nullable column.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9dc54b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[coderabbitai]

Walkthrough

This pull request adds timestamp tracking to the FeatureFlag entity. A database migration adds two timestamp columns (createdAt and updatedAt) to the public.FeatureFlag table with default values set to the current timestamp. The Prisma schema is updated correspondingly to include these fields with @default(now()) and @updatedAt directives for automatic timestamp management.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description is incomplete. It lacks required sections including Closes #issue reference, checklist, Testing section, and Changelog section from the template.	Complete the pull request description by following the template: add issue reference, fill the checklist, document testing steps, and provide a changelog entry.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Title check	✅ Passed	The title directly and accurately describes the main change: adding createdAt and updatedAt timestamp fields to the FeatureFlag model.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[claude]

PR Review: FeatureFlag add createdAt and updatedAt

Summary

This PR adds createdAt and updatedAt timestamp columns to the FeatureFlag model for debugging and auditing purposes. The change is minimal and focused.

Code Quality ✅

• Clean, minimal change that follows existing patterns in the codebase
• Prisma schema correctly uses @default(now()) for createdAt and @updatedAt for automatic update tracking

Potential Issue ⚠️

Migration mismatch with schema: There's a subtle issue between the migration and the Prisma schema:

• Schema: updatedAt DateTime @updatedAt - This tells Prisma to automatically update this field on every update
• Migration: "updatedAt" TIMESTAMP(3) NOT NULL DEFAULT CURRENT_TIMESTAMP - Sets default to current timestamp

The migration is correct for initial data (existing rows get now() as documented in the PR description). However, it's worth noting that the @updatedAt behavior is handled at the Prisma client level, not the database level. This means:

1. ✅ Updates via Prisma will correctly update updatedAt
2. ⚠️ Direct SQL updates won't automatically update updatedAt

This is likely fine for your use case since the FeatureFlag model is updated via Prisma's upsert in featureFlags.server.ts:68-79. Just worth being aware of.

Performance ✅

• No performance concerns - adding columns with defaults is efficient
• No index changes, which is appropriate for a small table like feature flags

Security ✅

• No security concerns

Test Coverage

• No new tests, which is appropriate for this change - the existing upsert pattern in featureFlags.server.ts will work correctly with the new fields

Verdict

Looks good to merge! 👍

The change is straightforward, follows existing conventions, and achieves the stated goal of adding timestamps for debugging and auditing.

[vibe-kanban-cloud]

Review Complete

Your review story is ready!

View Story

Comment !reviewfast on this PR to re-generate the story.