summaryrefslogtreecommitdiffstats
path: root/docs/submodules/integration
diff options
context:
space:
mode:
authorIttay Stern <ittay.stern@att.com>2019-10-10 08:22:51 +0000
committerGerrit Code Review <gerrit@onap.org>2019-10-10 08:22:51 +0000
commit1a235a2d2d0934be00e24e1352fbbc1a351bf269 (patch)
treea85f8a8ac1ab113df66471cff93c13467fec6b33 /docs/submodules/integration
parent79aeeb7611f2e1a94fee61829ed2c31edfadf3f2 (diff)
Update git submodules
* Update docs/submodules/vid.git from branch 'master' to 012975b2349ba5cc7c8434195b59459b8b0a0e89 - Merge changes from topics "VID-30", "VID-37" * changes: Add the "@Override" annotation. Replace "==" with "===". - Add the "@Override" annotation. 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: I90f07b6da5934fcba0c6d4106a75684438d8bb4b Signed-off-by: anushadasari <danush10@in.ibm.com> - Replace "==" with "===". The == and != operators do type coercion before comparing values. This is bad because it can mask type errors. For example, it evaluates ' \t\r\n' == 0 as true. It is best to always use the side-effect-less === and !== operators instead. Issue-ID: VID-656 Change-Id: If93fe032fae618bb0bd7112c24a0e4d3acab6337 Signed-off-by: anushadasari <danush10@in.ibm.com>
Diffstat (limited to 'docs/submodules/integration')
0 files changed, 0 insertions, 0 deletions