Med Java

User Tools

Site Tools

Trace:
java-script:console-table-error-assert-group

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
java-script:console-table-error-assert-group [2023/08/09 20:24] – removed - external edit (Unknown date) 127.0.0.1java-script:console-table-error-assert-group [2023/08/09 20:33] (current) – odefta
Line 1: Line 1:
 +====== Java Script Console Error, Table, Assert, Group ======
  
 +===== Console table =====
 +
 +Along with console.log, console.info, console.warn and console.error, there is **console.table** which is very useful to print data in a tabular format (for objects, arrays and arrays of objects). \\ 
 +Example:
 +<code javascript ConsoleTable.html>
 +<!DOCTYPE html>
 +<html lang="en">
 +<head>
 +    <meta charset="UTF-8">
 +    <title>Console Table</title>
 +</head>
 +<body>
 +<script>
 +    const people = [
 +    { name: 'Alice', age: 30 },
 +    { name: 'Bob', age: 25 },
 +    { name: 'Charlie', age: 35 }
 +    ];
 +
 +    console.table(people);
 +</script>
 +</body>
 +</html>
 +</code>
 +
 +The output is:
 +{{:java-script:pasted:20230809-155119.png}}
 +
 +To filter some of the columns we can use console.table(people, **['name']**):
 +<code javascript ConsoleTableFilter.html>
 +<!DOCTYPE html>
 +<html lang="en">
 +<head>
 +    <meta charset="UTF-8">
 +    <title>Console Table</title>
 +</head>
 +<body>
 +<script>
 +    const people = [
 +    { name: 'Alice', age: 30 },
 +    { name: 'Bob', age: 25 },
 +    { name: 'Charlie', age: 35 }
 +    ];
 +
 +    console.table(people, ['name']);
 +</script>
 +</body>
 +</html>
 +</code>
 +
 +===== Console error =====
 +
 +**console.error** can be used to display an error in the console. It will be displayed with a red x in front of it.
 +\\ If we want to display the stack trace showing where the error was logged we can use **Error(...)**:
 +
 +<code javascript>
 +function myFunction() {
 +  console.error(Error('Something went wrong!'));
 +}
 +
 +myFunction();
 +
 +</code>
 +
 +When this code is run, it will log the error message "Something went wrong!" to the console, **along with a stack trace** showing where the error was logged. This can be useful when you want to log a specific error message along with the context in which the error occurred.
 +
 +===== Console assert =====
 +
 +The **console.assert()** method writes an error message to the console if the assertion is false. \\ 
 +**If the assertion is true, nothing happens.**
 +
 +Syntax:
 +<code>
 +console.assert(assertion, message, ...optionalParams);
 +</code>
 +
 +Params:
 +  * **assertion**: An expression that's expected to evaluate to true. If this expression evaluates to false, the message is written to the console.
 +  * **message**: A string containing the message you want to send to the console if the assertion fails.
 +  * **...optionalParams**: Additional JavaScript objects with which to replace substitution strings within message.
 +
 +Examples:
 +<code javascript>
 +console.assert(5 > 10, '5 is not greater than 10'); // This will log the message because the assertion is false
 +</code>
 +
 +<code javascript>
 +function add(a, b) {
 +  console.assert(typeof a === 'number' && typeof b === 'number', 'Both arguments must be numbers');
 +  return a + b;
 +}
 +add('5', 3); // This will log the message because one of the arguments is not a number
 +</code>
 +
 +<code javascript>
 +function divide(a, b) {
 +  console.assert(b !== 0, 'Division by zero is not allowed. Value of b:', b);
 +  return a / b;
 +}
 +
 +divide(10, 0); // This will log: "Division by zero is not allowed. Value of b: 0"
 +</code>
 +
 +<note warning>
 +While you can technically leave calls to console.assert() in **production code**, it's usually considered best practice to **remove or disable** such debugging and diagnostic code before deploying to production. \\ 
 +
 +In some browsers, calls to **console.assert()** (and other console methods) may have no effect in production, depending on user settings and browser configuration. In others, these calls might still generate output in the console, which could be seen by users who have their developer tools open. This can potentially leak information about the inner workings of your code, which might be of interest to malicious actors. \\ 
 +</note>
 +
 +<note tip>
 +One common approach to handle this is to have a build step in your deployment process that removes or comments out calls to console.assert() (and other debugging code) as part of the **[[java-script:minification-uglification|minification or uglification process]]**.
 +</note>
 +
 +===== Console group =====
 +
 +**console.group()** and **console.groupEnd()** are used in JavaScript to **group together related log messages**. \\ You can also nest groups inside other groups, creating a hierarchical view in the console. 
 +
 +Simple example:
 +<code>
 +console.group("Hello!")
 +console.log("First message");
 +console.log("Second message");
 +console.groupEnd();
 +</code>
 +
 +Output:
 +{{:java-script:pasted:20230809-202925.png}}
 +
 +Nested group example:
 +<code>
 +console.log("Starting logs");
 +
 +console.group("Outer Group");
 +console.log("Inside the outer group");
 +
 +console.group("Inner Group 1");
 +console.log("Inside the inner group 1");
 +console.groupEnd(); // Ends Inner Group 1
 +
 +console.group("Inner Group 2");
 +console.log("Inside the inner group 2");
 +console.groupEnd(); // Ends Inner Group 2
 +
 +console.groupEnd(); // Ends Outer Group
 +
 +console.log("Outside of all groups");
 +</code>
 +
 +Output:
 +{{:java-script:pasted:20230809-203033.png}}
 +
 +<note>
 +Using **console.groupCollapsed()** instead of console.group() can create a collapsible group that is closed by default.
 +</note>