Skip to content
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

V7: rename notifyReleaseStages option #649

Merged
merged 1 commit into from Nov 18, 2019

Conversation

bengourley
Copy link
Contributor

Updated the naming of the notifyReleaseStages option to be enabledReleaseStages to denote the fact that it reflects sessions as well as error reporting. Additionally tweaked the behaviour to match the new spec:

  • An empty list should be interpreted as all releaseStages being enabled
  • The default value should be an empty list (instead of null)

@bugsnagbot
Copy link
Collaborator

bugsnagbot commented Nov 18, 2019

@bugsnag/browser bundle size diff

Minified Minfied + Gzipped
Before 40.81 kB 12.20 kB
After 40.80 kB 12.19 kB
± -13 bytes -7 bytes

Generated by 🚫 dangerJS against 2e308ea

Updated the naming of the notifyReleaseStages option to be enabledReleaseStages to denote the fact
that it reflects sessions as well as error reporting. Additionally tweaked the behaviour to match
the new spec:
 - An empty list should be interpreted as all releaseStages being enabled
 - The
default value should be an empty list (instead of null)
@bengourley bengourley force-pushed the v7-rename-notify-release-stages branch from 14d1280 to 2e308ea Compare November 18, 2019 11:55
@bengourley bengourley merged commit a0aacb8 into v7 Nov 18, 2019
@bengourley bengourley deleted the v7-rename-notify-release-stages branch November 18, 2019 14:32
@bengourley bengourley mentioned this pull request Apr 14, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants