the closing parenthesis of a multi-line function call is on a new line.
1 | /* global wp, _customizePostPreviewedQueriedObject */ |
||
2 | jQuery( document ).ready( function() { |
||
3 | |||
4 | var self = { |
||
5 | queriedPost: ( ! _.isUndefined( _customizePostPreviewedQueriedObject ) ) ? _customizePostPreviewedQueriedObject : null |
||
6 | }; |
||
7 | |||
8 | // Send the queried post object to the Customizer pane when ready. |
||
9 | wp.customize.bind( 'preview-ready', function() { |
||
10 | wp.customize.preview.bind( 'active', function() { |
||
11 | wp.customize.preview.send( 'queried-post', self.queriedPost ); |
||
12 | } ); |
||
0 ignored issues
–
show
|
|||
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 |
If a function call spawns multiple lines, the coding standard suggests to move the closing parenthesis to a new line: