Understand authentication hydration, public routes, secure routes, editor, response, report, and integration modules.
Internal documentation. Keep this post restricted to authorized staff and operators.
Overview
Understand authentication hydration, public routes, secure routes, editor, response, report, and integration modules.
Key points
- App hydrates token and instance from localStorage.
- Public, generic-key, and secure dashboard routes are separated.
- API calls are centralized in src/utils/api/index.js.
- The editor is lazy-loaded.
- GenericSurvey owns public response resolution and persistence.
- SecureShell provides navigation and common branding.
Recommended procedure
- Use a non-production environment and a clean worktree.
- Run tests and the production build.
- Verify configuration, routes, dependencies, and observability.
- Deploy only with an explicit rollback and post-deploy verification plan.
Troubleshooting
A deep route returns 404
Configure single-page-application fallback to index.html.
The dashboard and API disagree
Reconcile the client contract with the authoritative server implementation before release.