nextcloud /
notes
These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
| 1 | import Vue from 'vue' |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 2 | import Vuex from 'vuex' |
||
|
0 ignored issues
–
show
'import' is only available in ES6 (use 'esversion: 6').
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code. Further Reading: Loading history...
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 3 | |||
| 4 | Vue.use(Vuex) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 5 | |||
| 6 | export default new Vuex.Store({ |
||
|
0 ignored issues
–
show
'export' is only available in ES6 (use 'esversion: 6').
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code. Further Reading: Loading history...
|
|||
| 7 | state: { |
||
| 8 | notes: [], |
||
| 9 | notesIds: {}, |
||
| 10 | }, |
||
| 11 | |||
| 12 | getters: { |
||
| 13 | noteExists: (state) => (id) => { |
||
|
0 ignored issues
–
show
'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code. Further Reading: Loading history...
|
|||
| 14 | return state.notesIds[id] !== undefined |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 15 | }, |
||
| 16 | |||
| 17 | getNote: (state) => (id) => { |
||
|
0 ignored issues
–
show
'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code. Further Reading: Loading history...
|
|||
| 18 | if (state.notesIds[id].error) { |
||
| 19 | OC.Notification.show( |
||
| 20 | state.notesIds[id].errorMessage, |
||
| 21 | { type: 'error' } |
||
| 22 | ) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 23 | return false |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 24 | } |
||
| 25 | return state.notesIds[id] |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 26 | }, |
||
| 27 | |||
| 28 | getCategories: (state) => (maxLevel, details) => { |
||
|
0 ignored issues
–
show
'arrow function syntax (=>)' is only available in ES6 (use 'esversion: 6').
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code. Further Reading: Loading history...
|
|||
| 29 | function nthIndexOf(str, pattern, n) { |
||
| 30 | let i = -1 |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 31 | while (n-- && i++ < str.length) { |
||
| 32 | i = str.indexOf(pattern, i) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 33 | if (i < 0) { |
||
| 34 | break |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 35 | } |
||
| 36 | } |
||
| 37 | return i |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 38 | } |
||
| 39 | |||
| 40 | let categories = {} |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 41 | let notes = state.notes |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 42 | for (let i = 0; i < notes.length; i += 1) { |
||
|
0 ignored issues
–
show
|
|||
| 43 | let cat = notes[i].category |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 44 | if (maxLevel > 0) { |
||
| 45 | let index = nthIndexOf(cat, '/', maxLevel) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 46 | if (index > 0) { |
||
| 47 | cat = cat.substring(0, index) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 48 | } |
||
| 49 | } |
||
| 50 | if (categories[cat] === undefined) { |
||
| 51 | categories[cat] = 1 |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 52 | } else { |
||
| 53 | categories[cat] += 1 |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 54 | } |
||
| 55 | } |
||
| 56 | let result = [] |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 57 | for (let category in categories) { |
||
|
0 ignored issues
–
show
|
|||
| 58 | if (details) { |
||
| 59 | result.push({ |
||
| 60 | name: category, |
||
| 61 | count: categories[category], |
||
| 62 | }) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 63 | } else if (category) { |
||
| 64 | result.push(category) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 65 | } |
||
| 66 | } |
||
| 67 | if (details) { |
||
| 68 | result.sort(function(a, b) { |
||
| 69 | return (a.name).localeCompare(b.name) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 70 | }) |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 71 | } else { |
||
| 72 | result.sort() |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 73 | } |
||
| 74 | return result |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 75 | }, |
||
| 76 | }, |
||
| 77 | |||
| 78 | mutations: { |
||
| 79 | add(state, updated) { |
||
|
0 ignored issues
–
show
|
|||
| 80 | let note = state.notesIds[updated.id] |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 81 | if (note) { |
||
| 82 | // don't update meta-data over full data |
||
| 83 | if (updated.content !== null || note.content === null) { |
||
| 84 | note.title = updated.title |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 85 | note.modified = updated.modified |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 86 | note.content = updated.content |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
|
|||
| 87 | note.favorite = updated.favorite |
||
|
0 ignored issues
–
show
There should be a semicolon.
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers. Further Readings: Loading history...
There were too many errors found in this file; checking aborted after 73%.
If JSHint finds too many errors in a file, it aborts checking altogether because it suspects a configuration issue. Further Reading: Loading history...
|
|||
| 88 | note.category = updated.category |
||
| 89 | note.error = updated.error |
||
| 90 | note.errorMessage = updated.errorMessage |
||
| 91 | } |
||
| 92 | } else { |
||
| 93 | state.notes.push(updated) |
||
| 94 | state.notesIds[updated.id] = updated |
||
| 95 | } |
||
| 96 | }, |
||
| 97 | |||
| 98 | remove(state, id) { |
||
| 99 | for (let i = 0; i < state.notes.length; i++) { |
||
| 100 | let note = state.notes[i] |
||
| 101 | if (note.id === id) { |
||
| 102 | state.notes.splice(i, 1) |
||
| 103 | delete state.notesIds[id] |
||
| 104 | break |
||
| 105 | } |
||
| 106 | } |
||
| 107 | }, |
||
| 108 | }, |
||
| 109 | |||
| 110 | actions: { |
||
| 111 | addAll(context, notes) { |
||
| 112 | for (let i = 0; i < notes.length; i++) { |
||
| 113 | context.commit('add', notes[i]) |
||
| 114 | } |
||
| 115 | }, |
||
| 116 | }, |
||
| 117 | }) |
||
| 118 |
Generally using ECMAScript 6 specific syntax is fine if you are sure that it is already supported by all engines which are supposed to run this code.
Further Reading: