-
Notifications
You must be signed in to change notification settings - Fork 11
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: add VAC reporting #886
Conversation
847a3a2
to
59902d2
Compare
New dependencies detected. Learn more about Socket for GitHub ↗︎
|
92fa06d
to
3217904
Compare
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.
Security review looks good
@bcaller I went with the route of using a hidden input to accept the private key, instead of using react-state. This should keep the value in the DOM, and ephemeral in the way that once the dialogue component goes away, so does whatever value that used to be there. |
Ah OK, so hiding the dialog causes the input to be deleted and when you open the dialog again it's reinitialised. Good. |
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.
Looks good thanks
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.
Looks good to me!
Front end part of: https://github.com/brave/ads-serve/issues/1617
Demo located on: https://github.com/brave/ads-serve/pull/3352