Skip to content

fix(telegram-subscriptions): delete unused fields - #103

Merged
shoom3301 merged 2 commits into
mainfrom
fix/cms-username
Oct 15, 2026
Merged

shoom3301 merged 2 commits into
mainfrom
fix/cms-username

Conversation

@shoom3301

Copy link
Copy Markdown
Contributor

No description provided.

@shoom3301 shoom3301 self-assigned this Oct 15, 2026

@kernelwhisperer kernelwhisperer left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

LGTM

@shoom3301 shoom3301 changed the title fix(telegram-subscriptions): delete unused username field fix(telegram-subscriptions): delete unused fields Oct 15, 2026

@shoom3301 shoom3301 left a comment

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

✅ AI Review (Claude Opus 5.5, worked ~1m): no blocking findings; columns will be dropped on deploy (intended)
  • Location: src/api/telegram-subscription/content-types/telegram-subscription/schema.json
  • Strapi 4.26.1 defaults to forceMigration: true, and config/database doesn't override it, so on deploy the schema sync drops username, first_name and photo_url from telegram_subscriptions, along with their data. Confirmed as intended: this data doesn't need to be kept.
  • Custom endpoints (getSubscriptions, getAccountSubscriptions, getAccountsByChatId) only select id, account, chatId, so their responses don't change.
  • linkViaBot stays compatible: a bot still sending firstName/username gets them ignored.

Note: [NITPICK] The PR title says "username", but 608eed2 also removes firstName and photoUrl. The existing approval was on ef1dfc9 (username only).

Generated using the pr-review skill from the CoW Protocol skills repo.

@shoom3301
shoom3301 merged commit cb77a25 into main Oct 15, 2026
3 checks passed
@shoom3301
shoom3301 deleted the fix/cms-username branch October 15, 2026 10:37
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.

3 participants