These results are based on our legacy PHP analysis, consider migrating to our new PHP analysis engine instead. Learn more
1 | /** |
||
2 | * Nextcloud - Tasks |
||
3 | * |
||
4 | * @author Raimund Schlüßler |
||
5 | * @copyright 2018 Raimund Schlüßler <[email protected]> |
||
6 | * |
||
7 | * This library is free software; you can redistribute it and/or |
||
8 | * modify it under the terms of the GNU AFFERO GENERAL PUBLIC LICENSE |
||
9 | * License as published by the Free Software Foundation; either |
||
10 | * version 3 of the License, or any later version. |
||
11 | * |
||
12 | * This library is distributed in the hope that it will be useful, |
||
13 | * but WITHOUT ANY WARRANTY; without even the implied warranty of |
||
14 | * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the |
||
15 | * GNU AFFERO GENERAL PUBLIC LICENSE for more details. |
||
16 | * |
||
17 | * You should have received a copy of the GNU Affero General Public |
||
18 | * License along with this library. If not, see <http://www.gnu.org/licenses/>. |
||
19 | * |
||
20 | */ |
||
21 | 'use strict' |
||
0 ignored issues
–
show
|
|||
22 | |||
23 | import Vue from 'vue' |
||
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...
|
|||
24 | 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...
|
|||
25 | import Requests from '../services/requests' |
||
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...
|
|||
26 | |||
27 | import { isTaskInList, searchSubTasks } from './storeHelper' |
||
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...
|
|||
28 | |||
29 | 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...
|
|||
30 | |||
31 | const state = { |
||
0 ignored issues
–
show
|
|||
32 | collections: [] |
||
33 | } |
||
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...
|
|||
34 | |||
35 | const getters = { |
||
0 ignored issues
–
show
|
|||
36 | |||
37 | /** |
||
38 | * Returns the count of tasks in a colllection |
||
39 | * |
||
40 | * Tasks have to |
||
41 | * - belong to a collection |
||
42 | * - be a root task |
||
43 | * - be uncompleted |
||
44 | * |
||
45 | * @param {Object} state The store data |
||
46 | * @param {Object} getters The store getters |
||
47 | * @param {Object} rootState The store root state |
||
48 | * @param {String} collectionId The id of the collection in question |
||
49 | * @returns {Integer} Count of tasks in the collection |
||
50 | */ |
||
51 | getCollectionCount: (state, getters, rootState) => (collectionId) => { |
||
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...
|
|||
52 | let count = 0 |
||
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...
|
|||
53 | rootState.calendars.calendars.forEach(calendar => { |
||
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...
|
|||
54 | let tasks = Object.values(calendar.tasks).filter(task => { |
||
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...
|
|||
55 | return isTaskInList(task, collectionId) && !task.related |
||
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...
|
|||
56 | }) |
||
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 | if (rootState.tasks.searchQuery) { |
||
58 | tasks = tasks.filter(task => { |
||
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...
|
|||
59 | if (task.matches(rootState.tasks.searchQuery)) { |
||
60 | return true |
||
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...
|
|||
61 | } |
||
62 | // We also have to show tasks for which one sub(sub...)task matches. |
||
63 | return searchSubTasks(task, rootState.tasks.searchQuery) |
||
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...
|
|||
64 | }) |
||
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 | count += tasks.length |
||
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...
|
|||
67 | }) |
||
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...
|
|||
68 | return count |
||
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...
|
|||
69 | } |
||
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 | |||
72 | const mutations = { |
||
0 ignored issues
–
show
|
|||
73 | /** |
||
74 | * Stores all available collections in the state |
||
75 | * |
||
76 | * @param {Object} state The store data |
||
77 | * @param {Object} payload The collections payload |
||
78 | */ |
||
79 | setCollections(state, payload) { |
||
0 ignored issues
–
show
|
|||
80 | state.collections = payload.collections |
||
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 | }, |
||
82 | |||
83 | /** |
||
84 | * Sets the visibility of a collection |
||
85 | * |
||
86 | * @param {Object} state The store data |
||
87 | * @param {Collection} newCollection The collection to update |
||
88 | */ |
||
89 | setVisibility(state, newCollection) { |
||
0 ignored issues
–
show
|
|||
90 | let collection = state.collections.find(search => search.id === newCollection.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...
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...
|
|||
91 | Vue.set(collection, 'show', newCollection.show) |
||
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...
|
|||
92 | } |
||
93 | } |
||
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...
|
|||
94 | |||
95 | const actions = { |
||
0 ignored issues
–
show
|
|||
96 | /** |
||
97 | * Requests all collections from the server |
||
98 | * |
||
99 | * @param {Object} commit The store mutations |
||
100 | * @returns {Promise} |
||
101 | */ |
||
102 | loadCollections({ commit }) { |
||
0 ignored issues
–
show
|
|||
103 | return new Promise(function(resolve) { |
||
104 | Requests.get(OC.generateUrl('apps/tasks/collections')) |
||
105 | .then(response => { |
||
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...
|
|||
106 | commit('setCollections', { |
||
107 | collections: response.data.data.collections |
||
108 | }) |
||
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...
|
|||
109 | resolve() |
||
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...
|
|||
110 | }) |
||
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...
|
|||
111 | }) |
||
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...
|
|||
112 | }, |
||
113 | |||
114 | /** |
||
115 | * Writes the visibility of a collection to the server |
||
116 | * |
||
117 | * @param {Object} context The store mutations |
||
118 | * @param {Collection} collection The collection to change |
||
119 | * @returns {Promise} |
||
120 | */ |
||
121 | setVisibility(context, collection) { |
||
0 ignored issues
–
show
|
|||
122 | context.commit('setVisibility', collection) |
||
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 93%.
If JSHint finds too many errors in a file, it aborts checking altogether because it suspects a configuration issue. Further Reading:
Loading history...
|
|||
123 | return new Promise(function() { |
||
124 | Requests.post(OC.generateUrl('apps/tasks/collection/{id}/visibility/{show}', collection), {}) |
||
125 | }) |
||
126 | } |
||
127 | } |
||
128 | |||
129 | export default { state, getters, mutations, actions } |
||
130 |
Requirement of semicolons purely is a coding style issue since JavaScript has specific rules about semicolons which are followed by all browsers.
Further Readings: