-
Notifications
You must be signed in to change notification settings - Fork 1.5k
[PM-24279] Utilize Policy vNext endpoint #16317
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
base: main
Are you sure you want to change the base?
Conversation
} catch (e) { | ||
this.toastService.showToast({ variant: "error", title: null, message: e.message }); | ||
return; | ||
if (await this.shouldUseVNextImplementation()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey @BrandonTreston , please review the architecture of this PR. Once I get your approval, I will add tests.
|
New Issues (29)Checkmarx found the following issues in this Pull Request
|
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-24279
📔 Objective
We introduce a Policy vNext endpoint that includes a breaking change in the request body. This new endpoint enables us to pass metadata to perform operations on the backend that are not associated with the policy record data. PR for the new endpoint.
Changes in this PR
📸 Screenshots
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes