* Update docs/submodules/vid.git from branch 'master'
to
0b6ca2b05ca0896ad4f9b2f4943b1fa9292e8dfb
- Add "@Override" annotation above method signature.
Using the @Override annotation is useful for two reasons :
It elicits a warning from the compiler if the annotated method doesn't actually override anything, as in the case of a misspelling.
It improves the readability of the source code by making it obvious that methods are overridden.
Issue-ID: VID-612
Change-Id: Ic628b85f7a3e4c08712c88298fa4620ecddce0cc
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I27deafe5e97d71be4b5b6501f3cda0a19769123b
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Ibf05db5e76be01c78cfac8196fcf4bb09dfa7709
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: Id3fd3e7baea856e8aab4c5c7c509a6c00bb44ced
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I45637083e88ac2e1c4cb27519a3116f2f5f792e8
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I2adee2c4d945cde39d796106fa6540d875b25219
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line
Issue-ID: VID-607
Change-Id: I6798e2fbf4439e5336e1af734aa762449454f04f
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I74a97be12bc5a110c4afd7f2d3eaf51b0ae707c8
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line
Issue-ID: VID-607
Change-Id: I351d26cab21fffe5925dd6bc64691166e5c3ea3d
Signed-off-by: anushadasari <danush10@in.ibm.com>
- Add a semicolon at the end of this statement.
In JavaScript, the semicolon (;) is optional as a statement separator, but omitting semicolons can be confusing, and lead to unexpected results because a semicolon is implicitly inserted at the end of each line.
Issue-ID: VID-607
Change-Id: I1fd965413585256c09e61c2a19b0651800e65eab
Signed-off-by: anushadasari <danush10@in.ibm.com>
Code Review / doc.git / commitdiff