-
Notifications
You must be signed in to change notification settings - Fork 1.6k
[PM-29518] Remove @ts-strict-ignore in overlay/inline-menu/content/autofill-inline-menu-content.service.ts #18155
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
…upMutationObserver
… and list so TS knows they are definitely assigned
…cks, last child now has a fallback to 0 for undefined
|
Great job! No new security vulnerabilities introduced in this pull request |
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #18155 +/- ##
==========================================
- Coverage 42.26% 42.25% -0.01%
==========================================
Files 3599 3599
Lines 104516 104515 -1
Branches 15776 15775 -1
==========================================
- Hits 44171 44166 -5
- Misses 58465 58468 +3
- Partials 1880 1881 +1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
…in-overlay-inline-menu-content-autofill-inline-menu-content-service-ts-8-err-687-loc-86-9
Changes in this PR impact the Autofill experience of the browser clientBIT has tested the core experience with these changes and all feature flags disabled. ✅ Fortunately, these BIT tests have passed! 🎉 |
Changes in this PR impact the Autofill experience of the browser clientBIT has tested the core experience with these changes and the feature flag configuration used by ✅ Fortunately, these BIT tests have passed! 🎉 |

🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-29518
📔 Objective
📸 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