chore: tornar core tenant-agnóstico com contrato e guardrails#116
Conversation
|
Warning Rate limit exceeded
⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (31)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
Project Scorecard |
|



Resumo
Implementa o baseline de desacoplamento multi-tenant no
core, removendo hardcodes de owner/paths, adicionando contrato de tenant e guardrail de CI para bloquear regressões.Mudanças principais
src/tenant/contract.ts(campos obrigatórios e validação runtime)src/index.ts)tenant-decoupling:scripts/security/validate-tenant-decoupling.shcheck:tenant-decouplingtenant-decouplingtest-autogenphase 0 para contexto explícito de tenant (hooks + CI)FORGE_DEPENDENT_PROJECTSValidação
npm run validate✅npm run build✅npm test -- --runInBand✅npm run check:tenant-decoupling✅Observações