notifyReleaseStages -> enabledReleaseStages #239
Merged
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.
This pull request refactors the configuration option for specifying which release stages should send errors to Bugsnag. The property and related methods have been renamed from
notifyReleaseStagestoenabledReleaseStagesthroughout the codebase, including classes, methods, documentation, tests, and configuration files. This change improves clarity and consistency in naming, making it easier to understand the intent of the setting.API and Configuration Refactor
ConfigurationfromnotifyReleaseStagestoenabledReleaseStages, and updated all related logic to use the new name. [1] [2]BugsnagandBugsnagAppenderclasses: methods, fields, and documentation now useenabledReleaseStagesinstead ofnotifyReleaseStages. Deprecated old setter methods and added new ones for the updated naming. [1] [2] [3] [4] [5] [6] [7]Test and Scenario Updates
enabledReleaseStagesinstead ofnotifyReleaseStages, including method names, assertions, and comments. [1] [2] [3] [4] [5] [6] [7] [8] [9]Configuration File Changes
<enabledReleaseStage>tags instead of<notifyReleaseStage>. [1] [2] [3]