oroinc /
platform
| Conditions | 1 |
| Paths | 1 |
| Total Lines | 84 |
| Lines | 0 |
| Ratio | 0 % |
| Changes | 1 | ||
| Bugs | 0 | Features | 0 |
Small methods make your code easier to understand, in particular if combined with a good name. Besides, if your method is small, finding a good name is usually much easier.
For example, if you find yourself adding comments to a method's body, this is usually a good sign to extract the commented part to a new method, and use the comment as a starting point when coming up with a good name for this new method.
Commonly applied refactorings include:
If many parameters/temporary variables are present:
| 1 | define(function(require) { |
||
| 2 | 'use strict'; |
||
| 3 | |||
| 4 | var $ = require('jquery'); |
||
| 5 | var BaseComponent = require('oroui/js/app/components/base/component'); |
||
| 6 | |||
| 7 | var ComponentNeedsB = BaseComponent.extend({ |
||
|
|
|||
| 8 | relatedSiblingComponents: { |
||
| 9 | componentB: 'component-b' |
||
| 10 | }, |
||
| 11 | |||
| 12 | /** |
||
| 13 | * @inheritDoc |
||
| 14 | */ |
||
| 15 | constructor: function ComponentNeedsB() { |
||
| 16 | ComponentNeedsB.__super__.constructor.apply(this, arguments); |
||
| 17 | } |
||
| 18 | }); |
||
| 19 | |||
| 20 | var ComponentNeedsCE = BaseComponent.extend({ |
||
| 21 | relatedSiblingComponents: { |
||
| 22 | componentC: 'component-c', |
||
| 23 | componentE: 'component-e' |
||
| 24 | }, |
||
| 25 | |||
| 26 | /** |
||
| 27 | * @inheritDoc |
||
| 28 | */ |
||
| 29 | constructor: function ComponentNeedsCE() { |
||
| 30 | ComponentNeedsCE.__super__.constructor.apply(this, arguments); |
||
| 31 | } |
||
| 32 | }); |
||
| 33 | |||
| 34 | var ComponentNeedsA = BaseComponent.extend({ |
||
| 35 | relatedSiblingComponents: { |
||
| 36 | componentA: 'component-a' |
||
| 37 | }, |
||
| 38 | |||
| 39 | /** |
||
| 40 | * @inheritDoc |
||
| 41 | */ |
||
| 42 | constructor: function ComponentNeedsA() { |
||
| 43 | ComponentNeedsA.__super__.constructor.apply(this, arguments); |
||
| 44 | } |
||
| 45 | }); |
||
| 46 | |||
| 47 | var ComponentExtendNoNeedA = ComponentNeedsA.extend({ |
||
| 48 | relatedSiblingComponents: { |
||
| 49 | componentA: false |
||
| 50 | }, |
||
| 51 | |||
| 52 | /** |
||
| 53 | * @inheritDoc |
||
| 54 | */ |
||
| 55 | constructor: function ComponentExtendNoNeedA() { |
||
| 56 | ComponentExtendNoNeedA.__super__.constructor.apply(this, arguments); |
||
| 57 | } |
||
| 58 | }); |
||
| 59 | |||
| 60 | var ComponentNoNeeds = BaseComponent.extend({ |
||
| 61 | /** |
||
| 62 | * @inheritDoc |
||
| 63 | */ |
||
| 64 | constructor: function ComponentNoNeeds() { |
||
| 65 | ComponentNoNeeds.__super__.constructor.apply(this, arguments); |
||
| 66 | } |
||
| 67 | }); |
||
| 68 | |||
| 69 | var components = { |
||
| 70 | 'js/needs-b-component': ComponentNeedsB, |
||
| 71 | 'js/needs-ce-component': ComponentNeedsCE, |
||
| 72 | 'js/needs-a-component': ComponentNeedsA, |
||
| 73 | 'js/extend-no-need-a-component': ComponentExtendNoNeedA, |
||
| 74 | 'js/no-needs-component': ComponentNoNeeds |
||
| 75 | }; |
||
| 76 | |||
| 77 | return function(moduleName) { |
||
| 78 | var deferred = $.Deferred(); |
||
| 79 | setTimeout(function() { |
||
| 80 | deferred.resolve(components[moduleName]); |
||
| 81 | }, 0); |
||
| 82 | return deferred.promise(); |
||
| 83 | }; |
||
| 84 | }); |
||
| 85 |
Loading history...
This check looks for variables that are declared in multiple lines. There may be several reasons for this.
In the simplest case the variable name was reused by mistake. This may lead to very hard to locate bugs.
If you want to reuse a variable for another purpose, consider declaring it at or near the top of your function and just assigning to it subsequently so it is always declared.