Skip to content

Conversation

@lamppu
Copy link
Member

@lamppu lamppu commented Jan 16, 2026

Please see the individual commits for details.

Clearance library:
Screenshot from 2026-01-16 16-35-33

MainUI bulk conclusions view:
Screenshot from 2026-01-16 16-36-35

Package view with clearance group selector open:
Screenshot from 2026-01-16 16-37-13

@lamppu lamppu temporarily deployed to unittest-environment January 16, 2026 07:38 — with GitHub Actions Inactive
@lamppu lamppu temporarily deployed to test-environment January 16, 2026 07:38 — with GitHub Actions Inactive
@lamppu lamppu force-pushed the refactorings-for-clearance-items branch from 142836c to ae306d9 Compare January 16, 2026 12:15
@lamppu lamppu temporarily deployed to unittest-environment January 16, 2026 12:15 — with GitHub Actions Inactive
@lamppu lamppu force-pushed the refactorings-for-clearance-items branch from ae306d9 to 87a363b Compare January 16, 2026 13:13
@lamppu lamppu temporarily deployed to unittest-environment January 16, 2026 13:13 — with GitHub Actions Inactive
@lamppu lamppu temporarily deployed to test-environment January 16, 2026 13:13 — with GitHub Actions Inactive
lamppu added 12 commits January 16, 2026 15:20
Add extensions for the Playwright test fixture [1] and add some seeding
functions for upcoming tests. The fixture setup ensures that all test data
is properly removed after the tests, even with test failures. The seed
functions are also easily reusable through different tests.

Add a base fixture extension that includes extensions needed in all tests,
and make separate extensions for different routers for easier handling of
the router's path infix, and to allow different authentication contexts for
the tests, as the need for these may slightly differ based on which
router's tests are in question.

In the fixtures, code executed after `await use(...)` will run during
teardown after the test has finished.

[1]: https://playwright.dev/docs/test-fixtures#creating-a-fixture

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
…ess to

This will be used to populate a clearance group selector in the UI.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
The selector component shows the clearance groups that the user has write
or read access to, and allows to select a writable one. Any new clearance
items made will be added to the selected group.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
If the user has the realm role "app-user", and therefore has permission to
create clearance items, but doesn't have write access to any clearance
groups, show a message in the clearance item forms to instruct the user to
contact a system administrator.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
The clearance items will belong to groups and will be returned based on the
user's or a token's access rights.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
Also add the license conclusions created by the bulk conclusion to the
group.

The clearance items will belong to groups and will be returned based on the
user's or a token's access rights.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
…on edit

If the bulk conclusion edit results in new license conclusions being added
to the database, also sync the groups of the new license conclusions to
match the bulk conclusion's group(s).

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
The clearance items will belong to groups and will be returned based on the
user's or a token's access rights.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
Allow to filter by groups in the clearance item GET endpoints, and without
filters return all items from all groups the user has access to. Also
return the groups for the items in the GET responses.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
Show icons/badges representing the groups in the clearance library tables,
in the clearance inspector window in the `MainUI` package view, and in the
clearance listings for the package in the `MainUI` tabs.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
For the affected files listing, and the bulk conclusion detail endpoint,
check that the user has access to a group that the item belongs to.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
@lamppu lamppu force-pushed the refactorings-for-clearance-items branch from 87a363b to bb25b2b Compare January 16, 2026 13:26
@lamppu lamppu temporarily deployed to unittest-environment January 16, 2026 13:26 — with GitHub Actions Inactive
@lamppu lamppu temporarily deployed to test-environment January 16, 2026 13:26 — with GitHub Actions Inactive
In the initial implementation of the endpoint, all clearance items of
the curator are added to the specified clearance group, and removed
from other groups. The endpoint can later be extended for example to
allow moving/copying only specific items between groups.

Signed-off-by: Johanna Lamppu <johanna.lamppu@doubleopen.org>
@lamppu lamppu force-pushed the refactorings-for-clearance-items branch from bb25b2b to 331c10f Compare January 16, 2026 13:57
@lamppu lamppu deployed to test-environment January 16, 2026 13:57 — with GitHub Actions Active
@lamppu lamppu deployed to unittest-environment January 16, 2026 13:57 — with GitHub Actions Active
@lamppu lamppu marked this pull request as ready for review January 16, 2026 14:42
@lamppu lamppu requested a review from a team as a code owner January 16, 2026 14:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants