fix: made setTls more generic, updateConfig can modify all config…

… options

* Fixes #3

[ci skip]

src/QUICServer.ts

@@ -280,13 +280,15 @@ class QUICServer extends EventTarget {
   }
 
   /**
-   * This updates the `tlsConfig` used when new connections are established.
-   * It will not affect existing connections, they will keep using the old `tlsconfig`
-   * @param tlsConfig
+   * This updates the `QUICConfig` used when new connections are established.
+   * Only the parameters that are provided are updated.
+   * It will not affect existing connections, they will keep using the old `QUICConfig`
    */
-  public setTLSConfig(tlsConfig: TlsConfig): void {
-    // tlsConfig is an object, spread to copy and avoid object mutation
-    this.config.tlsConfig = { ...tlsConfig };
+  public updateConfig(config: Partial<QUICConfig>): void {
+    this.config = {
+      ...this.config,
+      ...config,
+    };
   };
 
   /**

tests/QUICClient.test.ts

@@ -254,7 +254,9 @@ describe(QUICClient.name, () => {
         logger: logger.getChild(QUICClient.name),
       });
       const peerCertChainInitial = client1.connection.conn.peerCertChain()
-      server.setTLSConfig(certFixtures.tlsConfigFileRSA2)
+      server.updateConfig({
+        tlsConfig: certFixtures.tlsConfigFileRSA2
+      })
       // The existing connection's certs should be unchanged
       const peerCertChainNew = client1.connection.conn.peerCertChain()
       expect(peerCertChainNew![0].toString()).toStrictEqual(peerCertChainInitial![0].toString());
@@ -281,7 +283,9 @@ describe(QUICClient.name, () => {
         logger: logger.getChild(QUICClient.name),
       });
       const peerCertChainInitial = client1.connection.conn.peerCertChain()
-      server.setTLSConfig(certFixtures.tlsConfigFileRSA2)
+      server.updateConfig({
+        tlsConfig: certFixtures.tlsConfigFileRSA2
+      })
       // Starting a new connection has a different peerCertChain
       const client2 = await QUICClient.createQUICClient({
         host: '::ffff:127.0.0.1' as Host,