feat(dashboard): implement widget item api v2

[st3iny]

• Resolves: none

Summary

This API enables the dashboard to render all widgets from the API data alone without having apps to provide their own bundles. This saves a lot of traffic and execution time as a lot less javascript has to be parsed on the frontend.

This is already done on the clients. However, the dashboard requires some extra logic and data as its widgets tend to be more sophisticated. To prevent breaking all apps and clients new API (v2) was introduced allowing each app and each client to migrate at their own pace.

Profiling results

Perceived loading time: Time from hitting refresh until all dashboard widgets finished loading.
No cache: Simulates a new visitor or a visitor returning after a long time. Cache is disabled in Chrome DevTools to force the browser to redownload all assets.
Cache: Simulates a user that often uses Nextcloud. Browser cache is enabled.

Tests were run on the same instance with exactly the same calendar, mail and spreed data etc.

Before

Without cache

Time until all widgets finised loading: 4284 ms

Chrome network stats:

151 requests
36.8 MB transferred
36.8 MB resources
DOMContentLoaded: 2.09 s
Load: 3.72 s

With cache

Time until all widgets finised loading: 3836 ms

Chrome network stats:

190 requests
126 kB transferred
36.6 MB resources
DOMContentLoaded: 1.34 s
Load: 2.76 s

After

Without cache

Time until all widgets finished loading: 2995 ms

Chrome network stats:

111 requests
29.0 MB transferred
28.9 MB resources
DOMContentLoaded: 1.63 s
Load: 3.05 s

With cache

Time until all widgets finished loading: 1500 ms

Chrome network stats:

132 requests
75.8 kB transferred
28.9 MB resources
DOMContentLoaded: 919 ms
Load: 1.53 s

TODO

• ...

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)

[provokateurin]

API changes LGTM

[nickvergessen]

Needs a rebase, but otherwise seems fine and functional

[st3iny]

/backport 6982597 to stable27

[nickvergessen]

Conflicting files
dist/settings-users-8351.js
dist/settings-users-8351.js.map
dist/settings-vue-settings-apps-users-management.js
dist/settings-vue-settings-apps-users-management.js.map 

Rebasing

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b fix/foo-stable27
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

[AndyScherzinger]

/backport 6982597 to stable27

[nickvergessen]

Will have to do it manually, the OpenAPI stuff does not exist on stable27

[nickvergessen]

PS I'm on it aklready

[backportbot-nextcloud]

The backport to stable27 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable27
git pull origin stable27
# Create the new backport branch
git checkout -b fix/foo-stable27
# Cherry pick the change from the commit sha1 of the change against the default branch# This might cause conflicts. Resolve them.
git cherry-pick abc123
# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable27

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport