@effect/opentelemetry 0.43.1 → 0.43.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +2 -61
- package/package.json +2 -2
package/README.md
CHANGED
|
@@ -1,64 +1,5 @@
|
|
|
1
|
-
#
|
|
2
|
-
|
|
3
|
-
Welcome to Effect, a powerful TypeScript framework that provides a fully-fledged functional effect system with a rich standard library.
|
|
4
|
-
|
|
5
|
-
# Requirements
|
|
6
|
-
|
|
7
|
-
- TypeScript 5.0 or newer
|
|
8
|
-
- The `strict` flag enabled in your `tsconfig.json` file
|
|
9
|
-
|
|
10
|
-
```
|
|
11
|
-
{
|
|
12
|
-
// ...
|
|
13
|
-
"compilerOptions": {
|
|
14
|
-
// ...
|
|
15
|
-
"strict": true,
|
|
16
|
-
}
|
|
17
|
-
}
|
|
18
|
-
```
|
|
1
|
+
# `@effect/opentelemetry`
|
|
19
2
|
|
|
20
3
|
## Documentation
|
|
21
4
|
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
## Introduction to Effect
|
|
25
|
-
|
|
26
|
-
To get started with Effect, watch our introductory video on YouTube. This video provides an overview of Effect and its key features, making it a great starting point for newcomers:
|
|
27
|
-
|
|
28
|
-
[](https://youtu.be/SloZE4i4Zfk)
|
|
29
|
-
|
|
30
|
-
## Connect with Our Community
|
|
31
|
-
|
|
32
|
-
Join our vibrant community on Discord to interact with fellow developers, ask questions, and share your experiences. Here's the invite link to our Discord server: [Join Effect's Discord Community](https://discord.gg/hdt7t7jpvn).
|
|
33
|
-
|
|
34
|
-
## API Reference
|
|
35
|
-
|
|
36
|
-
For detailed information on the Effect API, please refer to our [API Reference](https://effect-ts.github.io/effect/).
|
|
37
|
-
|
|
38
|
-
## Pull Requests
|
|
39
|
-
|
|
40
|
-
We welcome contributions via pull requests! Here are some guidelines to help you get started:
|
|
41
|
-
|
|
42
|
-
1. Fork the repository and clone it to your local machine.
|
|
43
|
-
2. Create a new branch for your changes: `git checkout -b my-new-feature`.
|
|
44
|
-
3. Ensure you have the required dependencies installed by running: `pnpm install` (assuming pnpm version `8.x`).
|
|
45
|
-
4. Make your desired changes and, if applicable, include tests to validate your modifications.
|
|
46
|
-
5. Run the following commands to ensure the integrity of your changes:
|
|
47
|
-
- `pnpm check`: Verify that the code compiles.
|
|
48
|
-
- `pnpm test`: Execute the tests.
|
|
49
|
-
- `pnpm circular`: Confirm there are no circular imports.
|
|
50
|
-
- `pnpm lint`: Check for code style adherence (if you happen to encounter any errors during this process, you can use `pnpm lint-fix` to automatically fix some of these style issues).
|
|
51
|
-
- `pnpm dtslint`: Run type-level tests.
|
|
52
|
-
- `pnpm docgen`: Update the automatically generated documentation.
|
|
53
|
-
6. Create a changeset for your changes: before committing your changes, create a changeset to document the modifications. This helps in tracking and communicating the changes effectively. To create a changeset, run the following command: `pnpm changeset`. Always choose the `patch` option when prompted (please note that we are currently in pre-release mode).
|
|
54
|
-
7. Commit your changes: after creating the changeset, commit your changes with a descriptive commit message: `git commit -am 'Add some feature'`.
|
|
55
|
-
8. Push your changes to your fork: `git push origin my-new-feature`.
|
|
56
|
-
9. Open a pull request against our `main` branch.
|
|
57
|
-
|
|
58
|
-
### Pull Request Guidelines
|
|
59
|
-
|
|
60
|
-
- Please make sure your changes are consistent with the project's existing style and conventions.
|
|
61
|
-
- Please write clear commit messages and include a summary of your changes in the pull request description.
|
|
62
|
-
- Please make sure all tests pass and add new tests as necessary.
|
|
63
|
-
- If your change requires documentation, please update the relevant documentation.
|
|
64
|
-
- Please be patient! We will do our best to review your pull request as soon as possible.
|
|
5
|
+
- **API Reference**: [View the full documentation](https://effect-ts.github.io/effect/docs/opentelemetry).
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@effect/opentelemetry",
|
|
3
|
-
"version": "0.43.
|
|
3
|
+
"version": "0.43.2",
|
|
4
4
|
"description": "OpenTelemetry integration for Effect",
|
|
5
5
|
"license": "MIT",
|
|
6
6
|
"repository": {
|
|
@@ -17,7 +17,7 @@
|
|
|
17
17
|
"@opentelemetry/sdk-trace-node": "^1.22",
|
|
18
18
|
"@opentelemetry/sdk-trace-web": "^1.22",
|
|
19
19
|
"@opentelemetry/semantic-conventions": "^1.24.1",
|
|
20
|
-
"effect": "^3.12.
|
|
20
|
+
"effect": "^3.12.12"
|
|
21
21
|
},
|
|
22
22
|
"peerDependenciesMeta": {
|
|
23
23
|
"@opentelemetry/sdk-metrics": {
|