fix(core): update

ts/smartstatus.classes.http.3xx.ts

@@ -1,4 +1,4 @@
-import { HttpStatus, TStatusGroup } from './smartstatus.classes.http'
+import { HttpStatus, TStatusGroup } from './smartstatus.classes.http';
 
 export class status300 extends HttpStatus {
   constructor() {
@@ -9,7 +9,7 @@ export class status300 extends HttpStatus {
         (via agent-driven content negotiation).
         For example, this code could be used to present multiple video format options,
         to list files with different filename extensions, or to suggest word-sense disambiguation.`
-    })
+    });
   }
 }
 
@@ -19,7 +19,7 @@ export class status301 extends HttpStatus {
       code: 301,
       text: 'Moved Permanently',
       description: `This and all future requests should be directed to the given URI.`
-    })
+    });
   }
 }
 
@@ -34,7 +34,7 @@ export class status302 extends HttpStatus {
         [20] but popular browsers implemented 302 with the functionality of a 303 See Other.
         Therefore, HTTP/1.1 added status codes 303 and 307 to distinguish between the two behaviours.[21]
         However, some Web applications and frameworks use the 302 status code as if it were the 303.`
-    })
+    });
   }
 }
 
@@ -47,7 +47,7 @@ export class status303 extends HttpStatus {
         When received in response to a POST (or PUT/DELETE),
         the client should presume that the server has received the data and should issue a redirect
         with a separate GET message.`
-    })
+    });
   }
 }
 
@@ -60,7 +60,7 @@ export class status304 extends HttpStatus {
         since the version specified by the request headers If-Modified-Since or If-None-Match.
         In such case, there is no need to retransmit the resource since the client
         still has a previously-downloaded copy.`
-    })
+    });
   }
 }
 
@@ -73,7 +73,7 @@ export class status305 extends HttpStatus {
         the address for which is provided in the response. Many HTTP clients (such as Mozilla[25]
         and Internet Explorer) do not correctly handle responses with this status code,
         primarily for security reasons.`
-    })
+    });
   }
 }
 
@@ -83,7 +83,7 @@ export class status306 extends HttpStatus {
       code: 306,
       text: 'Switch Proxy',
       description: `No longer used. Originally meant "Subsequent requests should use the specified proxy."`
-    })
+    });
   }
 }
 
@@ -97,7 +97,7 @@ export class status307 extends HttpStatus {
       In contrast to how 302 was historically implemented,
       the request method is not allowed to be changed when reissuing the original request.
       For example, a POST request should be repeated using another POST request.`
-    })
+    });
   }
 }
 
@@ -109,6 +109,6 @@ export class status308 extends HttpStatus {
       description: `The request and all future requests should be repeated using another URI.
       307 and 308 parallel the behaviors of 302 and 301, but do not allow the HTTP method to change.
       So, for example, submitting a form to a permanently redirected resource may continue smoothly.`
-    })
+    });
   }
 }