@backstage/plugin-events-backend-test-utils 0.1.24-next.2 → 0.1.24
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/CHANGELOG.md +41 -0
- package/package.json +3 -3
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,46 @@
|
|
|
1
1
|
# @backstage/plugin-events-backend-test-utils
|
|
2
2
|
|
|
3
|
+
## 0.1.24
|
|
4
|
+
|
|
5
|
+
### Patch Changes
|
|
6
|
+
|
|
7
|
+
- 56969b6: Add new `EventsService` as well as `eventsServiceRef` for the new backend system.
|
|
8
|
+
|
|
9
|
+
**Summary:**
|
|
10
|
+
|
|
11
|
+
- new:
|
|
12
|
+
`EventsService`, `eventsServiceRef`, `TestEventsService`
|
|
13
|
+
- deprecated:
|
|
14
|
+
`EventBroker`, `EventPublisher`, `EventSubscriber`, `DefaultEventBroker`, `EventsBackend`,
|
|
15
|
+
most parts of `EventsExtensionPoint` (alpha),
|
|
16
|
+
`TestEventBroker`, `TestEventPublisher`, `TestEventSubscriber`
|
|
17
|
+
|
|
18
|
+
Add the `eventsServiceRef` as dependency to your backend plugins
|
|
19
|
+
or backend plugin modules.
|
|
20
|
+
|
|
21
|
+
**Details:**
|
|
22
|
+
|
|
23
|
+
The previous implementation using the `EventsExtensionPoint` was added in the early stages
|
|
24
|
+
of the new backend system and does not respect the plugin isolation.
|
|
25
|
+
This made it not compatible anymore with the new backend system.
|
|
26
|
+
|
|
27
|
+
Additionally, the previous interfaces had some room for simplification,
|
|
28
|
+
supporting less exposure of internal concerns as well.
|
|
29
|
+
|
|
30
|
+
Hereby, this change adds a new `EventsService` interface as replacement for the now deprecated `EventBroker`.
|
|
31
|
+
The new interface does not require any `EventPublisher` or `EventSubscriber` interfaces anymore.
|
|
32
|
+
Instead, it is expected that the `EventsService` gets passed into publishers and subscribers,
|
|
33
|
+
and used internally. There is no need to expose anything of that at their own interfaces.
|
|
34
|
+
|
|
35
|
+
Most parts of `EventsExtensionPoint` (alpha) are deprecated as well and were not usable
|
|
36
|
+
(by other plugins or their modules) anyway.
|
|
37
|
+
|
|
38
|
+
The `DefaultEventBroker` implementation is deprecated and wraps the new `DefaultEventsService` implementation.
|
|
39
|
+
Optionally, an instance can be passed as argument to allow mixed setups to operate alongside.
|
|
40
|
+
|
|
41
|
+
- Updated dependencies
|
|
42
|
+
- @backstage/plugin-events-node@0.3.0
|
|
43
|
+
|
|
3
44
|
## 0.1.24-next.2
|
|
4
45
|
|
|
5
46
|
### Patch Changes
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@backstage/plugin-events-backend-test-utils",
|
|
3
|
-
"version": "0.1.24
|
|
3
|
+
"version": "0.1.24",
|
|
4
4
|
"description": "The plugin-events-backend-test-utils for @backstage/plugin-events-node",
|
|
5
5
|
"backstage": {
|
|
6
6
|
"role": "node-library"
|
|
@@ -32,9 +32,9 @@
|
|
|
32
32
|
"test": "backstage-cli package test"
|
|
33
33
|
},
|
|
34
34
|
"dependencies": {
|
|
35
|
-
"@backstage/plugin-events-node": "^0.3.0
|
|
35
|
+
"@backstage/plugin-events-node": "^0.3.0"
|
|
36
36
|
},
|
|
37
37
|
"devDependencies": {
|
|
38
|
-
"@backstage/cli": "^0.
|
|
38
|
+
"@backstage/cli": "^0.26.0"
|
|
39
39
|
}
|
|
40
40
|
}
|