fix(next.config): correct comment formatting for BACKEND_API_BASE_URL warning
- Updated comment in next.config.mjs to improve clarity regarding the implications of setting BACKEND_API_BASE_URL in the environment file. - Added "use client" directive in tableSortContext.ts to indicate client-side rendering for the context component.
This commit is contained in:
+1
-1
@@ -40,7 +40,7 @@ const nextConfig = {
|
||||
// Routing is host-based so neither deploy needs a custom env. A
|
||||
// `BACKEND_API_BASE_URL` env var (if set) overrides both — handy for local
|
||||
// dev pointing at e.g. http://localhost:8080/admin/v1.
|
||||
//! ⚠️ IMPORTANT: Adding BACKEND_API_BASE_URL to env file will break the multi-domain feature.
|
||||
// ! ⚠️ IMPORTANT: Adding BACKEND_API_BASE_URL to env file will break the multi-domain feature.
|
||||
const override = process.env.BACKEND_API_BASE_URL;
|
||||
if (override) {
|
||||
return [
|
||||
|
||||
Reference in New Issue
Block a user