fix: update Jitsi configuration handling for default values

- Refactored the Jitsi configuration logic to use nullish coalescing for default values in the frontend.
- Added a condition to reset configuration values to defaults when no configuration is available.
- Adjusted backend mutation to ensure consistent handling of the acceptSelfSignedCert parameter.
This commit is contained in:
2025-11-21 22:09:30 -03:00
parent 52823a9fac
commit 54089f5eca
2 changed files with 10 additions and 3 deletions

View File

@@ -29,8 +29,15 @@
domain = configAtual.data.domain || "";
appId = configAtual.data.appId || "sgse-app";
roomPrefix = configAtual.data.roomPrefix || "sgse";
useHttps = configAtual.data.useHttps || false;
acceptSelfSignedCert = configAtual.data.acceptSelfSignedCert || false;
useHttps = configAtual.data.useHttps ?? false;
acceptSelfSignedCert = configAtual.data.acceptSelfSignedCert ?? false;
} else if (configAtual === null) {
// Se não há configuração, resetar para valores padrão
domain = "";
appId = "sgse-app";
roomPrefix = "sgse";
useHttps = false;
acceptSelfSignedCert = false;
}
});