Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: change accessLevel to RoleId #145

Merged
merged 2 commits into from
Feb 6, 2025
Merged

feat: change accessLevel to RoleId #145

merged 2 commits into from
Feb 6, 2025

Conversation

Matte22
Copy link
Collaborator

@Matte22 Matte22 commented Jan 20, 2025

changes from accessLevel to roleId to match stig-manager API.

@csmig
Copy link
Member

csmig commented Jan 21, 2025

Watcher currently supports API versions from 1.2.7 (see MIN_API_VERSION in conts.js). To continue this support, it must continue to handle accessLevel properties.

Perhaps Watcher could call:
api.getDefinition('$.components.schemas.CollectionGrantProjected.properties')
and use the appropriate property depending on whether roleId or accessLevel is defined.

Maybe more simply, in the call to getUser() in api.js the response could be normalized so that a response with accessLevel is modified to use roleId.

Copy link

@cd-rite cd-rite merged commit 366eeae into main Feb 6, 2025
4 checks passed
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.

3 participants