-
Notifications
You must be signed in to change notification settings - Fork 251
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
Release v7.7.0 #1295
Merged
Merged
Release v7.7.0 #1295
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* next: (30 commits) Correct Gemfile use Use Maze 4.2.1 Remove Gemfile from Docker image Browser tests need MazeRunner v4.2.1+ Wind default MazeRunner version back to v3 Reorder steps Test docs updated for Browser TEMP COMMIT - use development MazeRunner Step name updates for v4 changes Update to latest Maze class name Use latest v4 Maze Runner Docker image Remove MazeRunner from local test util - to be documented separately Test fixture specific steps moved back into JS repo BROWSER envar no longer used Corrections for false failures Pass variables through Update to use new MR options Reinstate build steps Use separate endpoints Update line numbers for separation of endpoints ...
Update incorrect changelog years
docs(upgrading,react-native): iOS import statement
…may go out of date
test(core): add extractObject test
Tests: Update react-native e2e tests to use maze-runner v4
…age.json Co-authored-by: Joe Haines <[email protected]>
[PLAT-5796] Add support for Vue 3 without dropping Vue 2
…g files into the container
[PLAT-5651] Update react-native-cli tests to use Maze-runner v4
Use MR v3 style environment variables
Use maze runner image and general tidy
…race are inline scripts
…we missed the interactive event If Bugsnag is loaded after the readyState=interactive event has fired, it incorrectly assumed that inline scripts were still executing. This ensures that if the ready event is missed, it doesn't erroneously grab the last <script> on the page as the currentScript for errors that didn't originate in an inline script.
…eously set when Bugsnag is loaded async'ly
…ntent has not yet loaded
[PLAT-5980] Ensure inline <script> detection only includes script content when relevant
Update bugsnag-android dep to v5.6.2
bengourley
approved these changes
Feb 15, 2021
|
Minified | Minfied + Gzipped | |
---|---|---|
Before | 40.70 kB |
12.54 kB |
After | 40.76 kB |
12.57 kB |
± | +65 bytes |
+29 bytes |
code coverage diff
Ok | File | Lines | Branches | Functions | Statements |
---|---|---|---|---|---|
✅ | /home/runner/work/bugsnag-js/bugsnag-js/packages/core/lib/extract-object.js | 100% (+75%) |
100% (+100%) |
100% (+100%) |
100% (+75%) |
🔴 | /home/runner/work/bugsnag-js/bugsnag-js/packages/plugin-inline-script-content/inline-script-content.js | 81.91% (-1.96%) |
79.03% (-0.97%) |
78.57% (+0%) |
80.56% (-2.77%) |
🔴 | /home/runner/work/bugsnag-js/bugsnag-js/packages/plugin-vue/src/index.js | 94.44% (+3.01%) |
93.75% (+27.75%) |
80% (-8.89%) |
90.48% (+2.68%) |
✅ | /home/runner/work/bugsnag-js/bugsnag-js/packages/plugin-vue/src/vue.js | 100% (+100%) |
80% (+80%) |
100% (+100%) |
94.44% (+94.44%) |
✅ | /home/runner/work/bugsnag-js/bugsnag-js/packages/plugin-vue/src/vue2.js | 90.48% (+90.48%) |
52.78% (+52.78%) |
100% (+100%) |
84% (+84%) |
Total:
Lines | Branches | Functions | Statements |
---|---|---|---|
80.99%(+0.16%) | 69.88%(+0.4%) | 83.54%(+0.23%) | 79.9%(+0.08%) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
v7.7.0 (2021-02-15)
Changed
Fixed
onreadystatechange
interactive
event is missed. #1290