Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related: #2503
Summary
In preparation for alternative view modes like compact or hopefully the old non-compact mode an update to nextcloud-vue v8 is needed.
This enables the use of different layouts for NcAppContent (
vertical-
,horizontal-
andno-split
).no-split
came with nextcloud-vue 8.10.0,hoizontal-split
with 8.11.0.The needed changes were straightforward (nextcloud-libraries/nextcloud-vue#4223).
There are small visible changes:
Light theme v7:
Light theme v8:
Dark theme v7:
Dark theme v8:
Unit test problem (js-test)
The new library causes a problem with the unit-test (jest), which I bypassed with moduleNameMapper in package.json.
The problem seems that the new libraries have a wrapper and use the commonjs (.cjs) or esm (.mjs) version depending the import. The included library from the nextcloud-vue unist-util-visit only uses esm.
Besides the fact that the news app uses esm the jest tool uses commonjs and include the .cjs files, which results in the error
SyntaxError: Unexpected token 'export'
(see new stub file tests/javascript/helpers/unist-stub.js).ESM support in jest would be experimental ECMAScript Modules
Maybe @devlinjunker has more insights here and can check if my way to workaround is ok, because I'm not really familiar with the javascript unit tests yet.
Checklist