autocrm

Vasyka/autocrm

Fork 0

Commit Graph

Author	SHA1	Message	Date
Vasyka	3911012c65	feat(i18n): mega-wrap 494 raw RO strings + 269 lang entries + 161 human RU/163 EN Broad sweep across the whole codebase: - Blade views (39 files, 315 wraps): tag-text and title/placeholder/alt attributes wrapped with {{ __() }}. Excludes scripts, styles, @php, @verbatim, {{ }}, {!! !!}, comments to avoid touching interpolations. - PHP (54 files, 179 wraps): array 'key' => 'RO value' patterns and list items with diacritics wrapped with __(). Reverted __() inside const arrays (PHP disallows non-constant expressions). - Added 269 new keys to lang/{ru,en}.json (identity fallback for unknowns → 161 human RU + 163 EN translations added for the most common enums, stages, roles, statuses, payment methods, vehicle categories, warehouse, portal, form actions. Missing translations fall back to RO so the UI never breaks. All 306 tests pass; view cache compiles cleanly. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-07-15 05:53:22 +00:00
Vasyka	85ef2f6e00	Stage 13 — Notifications: Telegram bot + multi-channel + service reminders Schema: - clients.telegram_chat_id (linked via /start contact-share) - clients.notify_prefs (per-client channel order override) - service_reminders_sent (dedup ledger for the daily cron) Telegram (per tenant): - TelegramService (sendMessage, getMe, setWebhook with auto-generated secret) - Bot token stored in companies.settings.telegram.bot_token - Webhook /telegram/webhook/{slug} validates X-Telegram-Bot-Api-Secret-Token, matches client by last 9 digits of phone, persists chat_id, replies confirm - /start prompts share-contact; /stop unlinks chat_id NotificationDispatcher refactor: - Multi-channel: telegram first if chat_id + bot configured, then email - Backwards-compat with legacy boolean notify.{type} flags - 4 HTML-formatted Telegram messages (wo_ready with tracking link, payment, appointment, reminder) Service reminders: - `reminders:send` artisan command with --slug / --dry-run - Policy: vehicles whose last closed WO is older than reminder.after_days (default 365). Skips if sent within reminder.cooldown_days (default 30). - Schedule daily 09:00 Filament UI: - Settings page: Telegram bot token field + "Test bot" + "Set webhook" actions - Settings page: reminder_after_days + reminder_cooldown_days inputs - ClientResource: telegram_chat_id readonly badge Tests (6 new, all pass): - webhook links client via shared contact - webhook rejects wrong secret → 401 - dispatcher uses telegram when chat_id present (Http::fake) - dispatcher falls back to email otherwise - dispatcher returns false when no channel available - reminder cron respects 30-day cooldown Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>	2026-05-27 20:14:17 +00:00

Author

SHA1

Message

Date

Vasyka

3911012c65

feat(i18n): mega-wrap 494 raw RO strings + 269 lang entries + 161 human RU/163 EN

Broad sweep across the whole codebase:
- Blade views (39 files, 315 wraps): tag-text and title/placeholder/alt
  attributes wrapped with {{ __() }}. Excludes scripts, styles, @php,
  @verbatim, {{ }}, {!! !!}, comments to avoid touching interpolations.
- PHP (54 files, 179 wraps): array 'key' => 'RO value' patterns and
  list items with diacritics wrapped with __(). Reverted __() inside
  const arrays (PHP disallows non-constant expressions).
- Added 269 new keys to lang/{ru,en}.json (identity fallback for
  unknowns → 161 human RU + 163 EN translations added for the most
  common enums, stages, roles, statuses, payment methods, vehicle
  categories, warehouse, portal, form actions.

Missing translations fall back to RO so the UI never breaks. All 306
tests pass; view cache compiles cleanly.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-07-15 05:53:22 +00:00

Vasyka

85ef2f6e00

Stage 13 — Notifications: Telegram bot + multi-channel + service reminders

Schema:
- clients.telegram_chat_id (linked via /start contact-share)
- clients.notify_prefs (per-client channel order override)
- service_reminders_sent (dedup ledger for the daily cron)

Telegram (per tenant):
- TelegramService (sendMessage, getMe, setWebhook with auto-generated secret)
- Bot token stored in companies.settings.telegram.bot_token
- Webhook /telegram/webhook/{slug} validates X-Telegram-Bot-Api-Secret-Token,
  matches client by last 9 digits of phone, persists chat_id, replies confirm
- /start prompts share-contact; /stop unlinks chat_id

NotificationDispatcher refactor:
- Multi-channel: telegram first if chat_id + bot configured, then email
- Backwards-compat with legacy boolean notify.{type} flags
- 4 HTML-formatted Telegram messages (wo_ready with tracking link, payment,
  appointment, reminder)

Service reminders:
- `reminders:send` artisan command with --slug / --dry-run
- Policy: vehicles whose last closed WO is older than reminder.after_days
  (default 365). Skips if sent within reminder.cooldown_days (default 30).
- Schedule daily 09:00

Filament UI:
- Settings page: Telegram bot token field + "Test bot" + "Set webhook" actions
- Settings page: reminder_after_days + reminder_cooldown_days inputs
- ClientResource: telegram_chat_id readonly badge

Tests (6 new, all pass):
- webhook links client via shared contact
- webhook rejects wrong secret → 401
- dispatcher uses telegram when chat_id present (Http::fake)
- dispatcher falls back to email otherwise
- dispatcher returns false when no channel available
- reminder cron respects 30-day cooldown

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

2026-05-27 20:14:17 +00:00

2 Commits