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

Make references to NewRelic consistent #1795

Merged

Conversation

fchatterji
Copy link
Contributor

Before contributing, please read our contributing guidelines and code of conduct.

Overview

Pull request to make references to newrelic more consistent in the codebase, except in proto files and their dependencies

github issue: #1656

Submitter Checklist:

  • Include a link to the related GitHub issue, if applicable
  • Include a security review link, if applicable

Testing

The agent includes a suite of unit and functional tests which should be used to
verify your changes don't break existing functionality. These tests will run with
GitHub Actions when a pull request is made. More details on running the tests locally can be found
here for our unit tests,
and here for our functional tests.
For most contributions it is strongly recommended to add additional tests which
exercise your changes.

Reviewer Checklist

  • Perform code review
  • Add performance label
  • Perform appropriate level of performance testing
  • Confirm all checks passed
  • Add version label prior to acceptance

@CLAassistant
Copy link

CLAassistant commented Feb 6, 2023

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot added the community To tag external issues and PRs submitted by the community label Feb 6, 2023
@fchatterji
Copy link
Contributor Author

I fixed the failing tests, some renaming was needed

@hannahramadan
Copy link
Contributor

Hi @fchatterji 👋 Thanks for submitting this PR and congrats on your first open source contribution 🥳

Your PR looks great so far! There are a few more changes that we'd love to see if you're open to making those updates. I'm also happy to merge as-is.

Based on the sequel-related file name change of newrelic_instrumentation to new_relic_instrumentation, we will need to update a few other places that use this. Instances of newrelic_instrumentation should be changed to new_relic_instrumentation in the following files:

  • lib/new_relic/agent/instrumentation/sequel.rb
  • lib/sequel/extensions/newrelic_instrumentation.rb
  • test/multiverse/suites/sequel/sequel_extension_test.rb
  • test/multiverse/suites/sequel/sequel_helpers.rb

Copy link
Contributor

@hannahramadan hannahramadan left a comment

Choose a reason for hiding this comment

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

Thanks for making the additional updates. This looks great @fchatterji! I'll go ahead and merge your PR.

@hannahramadan hannahramadan merged commit 653ae9f into newrelic:dev Feb 8, 2023
@hannahramadan
Copy link
Contributor

Hey @fchatterji! We needed to make an update to our CI, which is why your dev merge failed. I wanted to follow up with the successful run of your PR. Thanks again for your contribution 😄

@fchatterji
Copy link
Contributor Author

@hannahramadan yes that's what i thought, great. By the way, I noticed that you still have some newrelic_instrumentation in lib/new_relic/agent/instrumentation/active_record.rb. If you want I could change those too.

@hannahramadan
Copy link
Contributor

Thanks for checking @fchatterji! All those instances of the string newrelic_instrumentation are found within the name of a method, either log_with_newrelic_instrumentation or log_without_newrelic_instrumentation. These are safe to leave as-is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community To tag external issues and PRs submitted by the community
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants