-
Notifications
You must be signed in to change notification settings - Fork 3
Rewrite #35
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: master
Are you sure you want to change the base?
Conversation
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. It is recommended to resolve "Warn" alerts too. Learn more about Socket for GitHub.
|
Due to CPU/Mem usage I've rewritten most of the data layer and ripped out the old reports system.
TODO:
[ ] - link to issue triage and tell users to login to triage issues in hover
[ ] - use scan data and sync scans against optimistic hovers when they overlap (follow on?); this will only be for logged in usage
[ ] - ruby hover support
[ ] - C# hover support