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:
AmirReza Jamali
2026-06-01 13:14:25 +03:30
parent de0e31bac5
commit 9424758af5
2 changed files with 3 additions and 1 deletions
+1 -1
View File
@@ -40,7 +40,7 @@ const nextConfig = {
// Routing is host-based so neither deploy needs a custom env. A // 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 // `BACKEND_API_BASE_URL` env var (if set) overrides both — handy for local
// dev pointing at e.g. http://localhost:8080/admin/v1. // 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; const override = process.env.BACKEND_API_BASE_URL;
if (override) { if (override) {
return [ return [
+2
View File
@@ -1,3 +1,5 @@
"use client";
import { createContext } from "react"; import { createContext } from "react";
export type SortDirection = "asc" | "desc"; export type SortDirection = "asc" | "desc";