Ilja authored 2 years ago and Haelwenn committed 2 years ago

We check for the first unhidden route, so the order needs to match the order on the sidebar. This is now fixed.

Ilja authored 2 years ago and Haelwenn committed 2 years ago

In view Users

Ilja authored 2 years ago and Haelwenn committed 2 years ago

A dropdown in Users and Statuses views.

Ilja authored 2 years ago and Haelwenn committed 2 years ago

This is a Dropdown in the Users tab.
There's still the problem that a non-admin is unaware when TagPolicy is enabled or not.
If that can be fixed, it will work properly with current implementation.

Ilja authored 2 years ago and Haelwenn committed 2 years ago

I noticed that the routes have an option `hidden`. This is what's used to show or hide items in the sidebar.
Now we set this option after login before adding the routes.

The redirect for root is now also set after login before adding the route.
That way we can set the route to the path corresponding with the first item in the sidebar.
When there's no unhidden route (e.g. when admin-fe doesn't know about any privilege the user has), the redirect goes to /401.

Ilja authored 2 years ago and Haelwenn committed 2 years ago

= This is a combination of 2 commits.
= This is the 1st commit message:

Atm you're redirected to /users after login even when you aren't privileged to any of the user actions. This should be addressed in a following commit.

It will only show the menu's on the left for which you are privileged. This can be depending on role (e.g. settings for admin) or privilege (e.g. user actions).

= This is the 2nd commit message:

It will only show the menu's on the left for which you are privileged. This is depending on privileges.

The redirect for root is now also set after login before adding the route.
That way we can set the route to the path corresponding with the first item in the sidebar.
When there's no unhidden route (e.g. when admin-fe doesn't know about any privilege the user has), the redirect goes to /401.

Ilja authored 2 years ago and Haelwenn committed 2 years ago

For some reason it checks if the roles are alredy filled in.
But roles can be empty now, so instead we also check if privileges are empty.

CI: Extract test coverage information

See merge request !322

fix(deps): update dependency element-ui to v2.15.12

See merge request !318

fix(deps): update dependency luxon to v3.1.1

See merge request !319

chore(deps): update dependency vue-style-loader to v4.1.3

See merge request !317

chore(deps): update dependency postcss to v8.4.20

See merge request !316

chore(deps): update dependency vue-jest to v4.0.1

See merge request !313

chore(deps): update dependency prosemirror-model to v1.18.3

See merge request !312

# Conflicts:
#   package.json

chore(deps): update dependency vue-loader to v15.10.1

See merge request !314

Partial: Make repository REUSE compliant

See merge request !291

chore(deps): update dependency postcss to v8.4.19

See merge request !305

fix(deps): update dependency luxon to v3.1.0

See merge request !306

chore(deps): update dependency @vue/test-utils to v1.3.3

See merge request !311

fix(deps): update dependency vue-router to v3.6.5

See merge request !292

chore(deps): update babel monorepo

See merge request !293

chore(deps): update dependency sass to v1.55.0

See merge request !288