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

Tom/rollup changes #40

Merged
merged 5 commits into from
Jul 2, 2019
Merged

Tom/rollup changes #40

merged 5 commits into from
Jul 2, 2019

Conversation

tomlongridge
Copy link
Contributor

@tomlongridge tomlongridge commented Jul 2, 2019

Goal

Contains fixes contributed by @fiskhandlarn and @chrisatomix to remove deprecation warnings when setting options and to make API key settable from wp-config. Also fixes broken links on settings page referencing the dashboard and account sign-up.

Changeset

Changed

  • bugsnag.php - added bugsnag_define_api_key method and filter to wrap calls to get API key option and return define, if set.
  • bugsnag.php - made bugsnagWordpress global for use in CLI scripts (see $bugsnagWordpress variable not available on CLI scripts #23)
  • views/settings.php - removed the form action as per recommendation.
  • views/settings.php - fixed references to bugsnag.com

Tests

  • Both changes manually tested with WP 5.2.2

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

@tomlongridge tomlongridge changed the base branch from master to next July 2, 2019 13:46
@tomlongridge tomlongridge marked this pull request as ready for review July 2, 2019 13:50
@tomlongridge tomlongridge requested a review from Cawllec July 2, 2019 13:51
Copy link
Contributor

@Cawllec Cawllec left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

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

4 participants