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

Fixes Typo In Enumeration #317

Merged
merged 3 commits into from
Feb 7, 2020
Merged

Conversation

kleinlieu
Copy link
Contributor

Goal

Found a typo in the spelling of one of the enums. I imagine this has downstream effects if anyone was using BSG_KSCDeleteOnSucess that would be guarded by a minor version upgrade since this will not be patch version compatible. Any suggestions appreciated.

Changeset

Changed

  • Fixes typo in the spelling of BSG_KSCDeleteOnSucess to BSG_KSCDeleteOnSuccess

Tests

Discussion

Alternative Approaches

Outstanding Questions

Linked issues

Review

For the submitter, initial self-review:

  • Commented on code changes inline explain the reasoning behind the approach
  • Reviewed the test cases added for completeness and possible points for discussion
  • A changelog entry was added for the goal of this pull request
  • Check the scope of the changeset - is everything in the diff required for the pull request?
  • This pull request is ready for:
    • Initial review of the intended approach, not yet feature complete
    • Structural review of the classes, functions, and properties modified
    • Final review

For the pull request reviewer(s), this changeset has been reviewed for:

  • Consistency across platforms for structures or concepts added or modified
  • Consistency between the changeset and the goal stated above
  • Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
  • Usage friction - is the proposed change in usage cumbersome or complicated?
  • Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
  • Concurrency concerns - if components are accessed asynchronously, what issues will arise
  • Thoroughness of added tests and any missing edge cases
  • Idiomatic use of the language

@snmaynard
Copy link
Contributor

We'll have to keep this PR waiting until we want to do a major release, as it is a breaking change - but it looks good, thanks for the contribution!

@kattrali kattrali changed the base branch from master to spec-compliance February 7, 2020 11:31
@kattrali kattrali merged commit 949e41a into bugsnag:spec-compliance Feb 7, 2020
robinmacharg pushed a commit that referenced this pull request Feb 12, 2020
@mattdyoung
Copy link

Released in v6.0.0.

Note: There are a number of breaking changes in v6.0.0 as part of an effort to improve the interface and make it more consistent across our error reporting libraries, so please refer to the upgrade guide:
https://github.com/bugsnag/bugsnag-cocoa/blob/master/UPGRADING.md

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.

4 participants