Issues (377)

modules/post-meta/customize-controls.js (12 issues)

1
jQuery( document ).ready( function() {
0 ignored issues
show
This file is missing a doc comment.
Loading history...
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
2
3
	var self;
4
5
	self = {
6
		queriedPost: new wp.customize.Value()
7
	};
8
9
	// Listen for queried-post messages from the preview.
10
	wp.customize.bind( 'ready', function() {
0 ignored issues
show
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
For multi-line function calls, each argument should be on a separate line.

For a function calls that spawns multiple lines, the coding style suggests to split arguments to separate lines like this:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
);
Loading history...
11
		wp.customize.previewer.bind( 'queried-post', function( queriedPost ) {
0 ignored issues
show
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
For multi-line function calls, each argument should be on a separate line.

For a function calls that spawns multiple lines, the coding style suggests to split arguments to separate lines like this:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
);
Loading history...
12
			self.queriedPost.set( queriedPost || false );
13
		} );
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
14
	} );
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
15
16
	// Listen for post
0 ignored issues
show
Inline comments must end in full-stops, exclamation marks, or question marks
Loading history...
17
	self.queriedPost.bind( function( newPost, oldPost ) {
0 ignored issues
show
The opening parenthesis of a multi-line function call should be the last content on the line.
Loading history...
18
		window.kirkiPost = false;
19
		if ( newPost || oldPost ) {
20
			window.kirkiPost = ( newPost ) ? newPost : oldPost;
21
		}
22
	} );
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
23
} );
0 ignored issues
show
For multi-line function calls, the closing parenthesis should be on a new line.

If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line:

someFunctionCall(
    $firstArgument,
    $secondArgument,
    $thirdArgument
); // Closing parenthesis on a new line.
Loading history...
24