Format Javascript indentation
This commit is contained in:
parent
689ca9b34c
commit
8cd05e8d8b
|
@ -1,16 +1,16 @@
|
|||
/**
|
||||
* Author: Vera Konigin
|
||||
* Site: https://groundedwren.neocities.org
|
||||
* Contact: vera@groundedwren.com
|
||||
*
|
||||
* File Description: Comments Control
|
||||
* Author: Vera Konigin
|
||||
* Site: https://groundedwren.neocities.org
|
||||
* Contact: vera@groundedwren.com
|
||||
*
|
||||
* File Description: Comments Control
|
||||
*/
|
||||
|
||||
/**
|
||||
* By default, any JavaScript code written is defined in the global namespace, which means it's accessible directly under the "window" element.
|
||||
* If you have a lot of scripts, this can lead to clutter and naming collisions (what if two different scripts use a variable called "i"? They can inadvertently mess each other up).
|
||||
* To get around this, we define the registerNamespace function in the global namespace, which just confines all the code in the function passed to it to a property under window.
|
||||
* That property is represented as the "path" parameter. It is passed to the function for ease of access.
|
||||
* By default, any JavaScript code written is defined in the global namespace, which means it's accessible directly under the "window" element.
|
||||
* If you have a lot of scripts, this can lead to clutter and naming collisions (what if two different scripts use a variable called "i"? They can inadvertently mess each other up).
|
||||
* To get around this, we define the registerNamespace function in the global namespace, which just confines all the code in the function passed to it to a property under window.
|
||||
* That property is represented as the "path" parameter. It is passed to the function for ease of access.
|
||||
*/
|
||||
function registerNamespace(path, nsFunc)
|
||||
{
|
||||
|
|
|
@ -5,14 +5,14 @@
|
|||
*
|
||||
* File Description: Gizmo for reading from Google Sheets.
|
||||
* Neocities editor users will see a lot of linter errors in this file, but none of them are real errors. The linter just doesn't understand some modern JS.
|
||||
*/
|
||||
*/
|
||||
|
||||
/**
|
||||
/**
|
||||
* By default, any JavaScript code written is defined in the global namespace, which means it's accessible directly under the "window" element.
|
||||
* If you have a lot of scripts, this can lead to clutter and naming collisions (what if two different scripts use a variable called "i"? They can inadvertently mess each other up).
|
||||
* To get around this, we define the registerNamespace function in the global namespace, which just confines all the code in the function passed to it to a property under window.
|
||||
* That property is represented as the "path" parameter. It is passed to the function for ease of access.
|
||||
*/
|
||||
*/
|
||||
function registerNamespace(path, nsFunc)
|
||||
{
|
||||
var ancestors = path.split(".");
|
||||
|
|
|
@ -4,14 +4,14 @@
|
|||
* Contact: vera@groundedwren.com
|
||||
*
|
||||
* File Description: A web component to site SVG icons easily
|
||||
*/
|
||||
*/
|
||||
|
||||
/**
|
||||
* By default, any JavaScript code written is defined in the global namespace, which means it's accessible directly under the "window" element.
|
||||
* If you have a lot of scripts, this can lead to clutter and naming collisions (what if two different scripts use a variable called "i"? They can inadvertently mess each other up).
|
||||
* To get around this, we define the registerNamespace function in the global namespace, which just confines all the code in the function passed to it to a property under window.
|
||||
* That property is represented as the "path" parameter. It is passed to the function for ease of access.
|
||||
*/
|
||||
*/
|
||||
function registerNamespace(path, nsFunc)
|
||||
{
|
||||
var ancestors = path.split(".");
|
||||
|
|
Loading…
Reference in New Issue