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

:✨⚗ [RUMF-1047] implement a RUM synthetics entry point #1188

Merged
merged 8 commits into from
Dec 7, 2021

Conversation

BenoitZugmeyer
Copy link
Member

@BenoitZugmeyer BenoitZugmeyer commented Nov 30, 2021

Motivation

Allows the Synthetics worker to inject RUM instances into test runs.

This PR superseds #1179

Changes

Provide a new entry point to be consumed by the Synthetics worker. As per RFC, this entry point won't define any global API, and won't ignore the init() call if the Synthetics worker is set to automatically inject RUM instance (as this is the instance that will be injected).

Testing

  • Local: tested with the e2e test app
  • Staging: can't be tested until a new release is published
  • Unit
  • End to end

I have gone over the contributing documentation.

This commit has nothing much to do with the PR, but was introduced in a
previous PR and still relevant.
@BenoitZugmeyer BenoitZugmeyer requested review from a team as code owners November 30, 2021 14:33
@BenoitZugmeyer BenoitZugmeyer changed the title ✨ [RUMF-1047] implement a RUM synthetics entry point :✨⚗ [RUMF-1047] implement a RUM synthetics entry point Nov 30, 2021
.eslintrc.js Outdated Show resolved Hide resolved
@codecov-commenter
Copy link

codecov-commenter commented Dec 2, 2021

Codecov Report

Merging #1188 (cc7d6e2) into main (8b19a16) will decrease coverage by 0.07%.
The diff coverage is 100.00%.

Impacted file tree graph

@@            Coverage Diff             @@
##             main    #1188      +/-   ##
==========================================
- Coverage   88.98%   88.90%   -0.08%     
==========================================
  Files         100      100              
  Lines        4285     4283       -2     
  Branches      969      970       +1     
==========================================
- Hits         3813     3808       -5     
- Misses        472      475       +3     
Impacted Files Coverage Δ
packages/logs/src/boot/logsPublicApi.ts 100.00% <ø> (ø)
packages/rum-core/src/boot/rumPublicApi.ts 93.69% <100.00%> (ø)
packages/core/src/tools/utils.ts 85.71% <0.00%> (-1.43%) ⬇️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8b19a16...cc7d6e2. Read the comment docs.

Fix the rum-slim package changing its directory structure because it has
no other module than entries/main:
https://github.com/Microsoft/TypeScript/wiki/FAQ#why-does---outdir-moves-output-after-adding-a-new-file

While this option is not required for other packages, it is still a good
failsafe to make sure the directory structure changes when moving
modules around.
@BenoitZugmeyer BenoitZugmeyer merged commit 685d92b into main Dec 7, 2021
@BenoitZugmeyer BenoitZugmeyer deleted the benoit/rum-synthetics-entry-point branch December 7, 2021 09:21
bcaudan pushed a commit that referenced this pull request Dec 7, 2021
* ✨ create a new entry point for synthetics

* 👷📝 validate and document existing build modes

This commit has nothing much to do with the PR, but was introduced in a
previous PR and still relevant.

* 📝 document the test to add some context, and fix a unit test title

* 👌 move RUM entry points

* 👌 move Logs entry point

* 👌 move RUM-slim entry point

* add tsconfig "rootDir"

Fix the rum-slim package changing its directory structure because it has
no other module than entries/main:
https://github.com/Microsoft/TypeScript/wiki/FAQ#why-does---outdir-moves-output-after-adding-a-new-file

While this option is not required for other packages, it is still a good
failsafe to make sure the directory structure changes when moving
modules around.
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