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

fix(rum-react): respect active flag in react integration #392

Merged
merged 4 commits into from
Aug 30, 2019

Conversation

vigneshshanmugam
Copy link
Member

@vigneshshanmugam vigneshshanmugam commented Aug 26, 2019

@codecov-io
Copy link

codecov-io commented Aug 28, 2019

Codecov Report

Merging #392 into master will decrease coverage by 0.09%.
The diff coverage is n/a.

@@            Coverage Diff            @@
##           master     #392     +/-   ##
=========================================
- Coverage   94.34%   94.24%   -0.1%     
=========================================
  Files          40       39      -1     
  Lines        1804     1791     -13     
  Branches      369      366      -3     
=========================================
- Hits         1702     1688     -14     
- Misses         97      100      +3     
+ Partials        5        3      -2
Impacted Files Coverage Δ
packages/rum/src/apm-base.js 92.78% <ø> (ø) ⬆️
packages/rum-angular/src/apm.service.ts
packages/rum-angular/src/index.ts
packages/rum-angular/src/apm-service.ts 81.81% <0%> (ø)
packages/rum-react/src/get-with-transaction.js 64.58% <0%> (+0.94%) ⬆️

Component
)
expect(WrappedComponent).toEqual(Component)
expect(transactionService.startTransaction).not.toHaveBeenCalled()
Copy link
Contributor

Choose a reason for hiding this comment

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

transactionService.startTransaction won't be called unless the component is rendered, so this probably always passes regardless of the test!

Copy link
Member Author

@vigneshshanmugam vigneshshanmugam Aug 29, 2019

Choose a reason for hiding this comment

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

I added the component to get rendered as well in previous line for double checking.

if you comment out the config.isActive check in the source, this test would fail which is expected.

Copy link
Contributor

@hmdhk hmdhk Aug 30, 2019

Choose a reason for hiding this comment

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

Ok, I thought maybe you intended to test with the component that you created in the test instead instead of the one created in TestComponent. Might be a bit better to group the code together so it's clear which checks are intended for those parts, but it's not very important.

it('should work if apm is disabled or not initialized', function() {
TestComponent(new ApmBase(createServiceFactory(), true))
TestComponent(new ApmBase(createServiceFactory(), false))
TestComponent(new ApmBase(serviceFactory, true))
Copy link
Contributor

Choose a reason for hiding this comment

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

This might be not related to this PR, but I'm not sure why this test passes. We probably should investigate why when we pass disable = true to ApmBase, it still calls startTransaction.

Do you happen to know?
Either way we can address that separately if you prefer.

Copy link
Member Author

@vigneshshanmugam vigneshshanmugam Aug 29, 2019

Choose a reason for hiding this comment

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

I guess it does not matter, component should get rendered if APM is enabled/disabled and we don't check if startTransaction is called or not. So I am not sure what is the issue here?

Copy link
Contributor

Choose a reason for hiding this comment

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

We probably can improve this test a bit, let's do it separately!

Copy link
Contributor

@hmdhk hmdhk left a comment

Choose a reason for hiding this comment

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

@vigneshshanmugam LGTM, let's merge once the tests are green!

@vigneshshanmugam vigneshshanmugam merged commit 6d7e9db into elastic:master Aug 30, 2019
@vigneshshanmugam vigneshshanmugam deleted the respect-active-flag branch August 30, 2019 08:48
David-Development pushed a commit to David-Development/apm-agent-rum-js that referenced this pull request Oct 20, 2021
* fix(rum-react): respect active flag in react integration

* remove logging when inactive

* add check for same component

* use apm.init instead of config init
devcorpio pushed a commit to bmorelli25/apm-agent-rum-js that referenced this pull request Jan 25, 2022
* fix(rum-react): respect active flag in react integration

* remove logging when inactive

* add check for same component

* use apm.init instead of config init
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.

framework integrations should respect active flag
3 participants