QRun-IO/qbit-marketing
3
0 Fork 0
Code Issues 1 Pull Requests 2 Actions Packages Projects Releases 7 Wiki Activity

feat(crm): qbit-crm 0.2.0 crm_* table names #17

Merged
KofTwentyTwo merged 3 commits from feature/crm-table-names into develop 2026-10-14 16:56:20 +00:00
Conversation 0 Commits 3 Files Changed 5
+212 -9
3 Commits
Author SHA1 Message Date
james.maes 1c0fa34e7c Merge remote-tracking branch 'origin/develop' into feature/crm-table-names 
# Conflicts:
#	CHANGELOG.md
 2026-10-14 11:52:54 -05:00
james.maesandClaude Opus 5.5 5dd68eb20b refactor(crm): crm_* table names only, no legacy fallback 
qbit-crm 0.2.0 renames its tables to crm_* with no compatibility shims
(owner decision via the coordinator), so the gateway uses the snake_case
names directly and drops the camelCase fallback and LEGACY_* constants.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-14 11:46:24 -05:00
james.maesandClaude Opus 5.5 d732cef626 feat(crm): resolve qbit-crm's snake_case table names, legacy fallback 
qbit-crm is renaming its tables to crm_* snake_case. QbitCrmGateway now
resolves each table from the instance at call time, preferring the
snake_case name and falling back to the legacy camelCase one, so either
qbit-crm generation works. Tests run the gateway against both schemes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
 2026-10-14 11:40:48 -05:00