@fluojs/notifications - npm Package Compare versions

Comparing version

1.0.0

1.0.1

+4

-4

package.json

		@@ -12,3 +12,3 @@ {
		],
		"version": "1.0.0",
		"version": "1.0.1",
		"private": false,
		@@ -40,5 +40,5 @@ "license": "MIT",
		"dependencies": {
		"@fluojs/di": "^1.0.0",
		"@fluojs/core": "^1.0.0",
		"@fluojs/runtime": "^1.0.0"
		"@fluojs/core": "^1.0.3",
		"@fluojs/di": "^1.0.3",
		"@fluojs/runtime": "^1.1.1"
		},
		@@ -45,0 +45,0 @@ "devDependencies": {

+2

-1

README.ko.md

		@@ -92,3 +92,3 @@ # @fluojs/notifications

		`NotificationsModule.forRoot(...)`와 `NotificationsModule.forRootAsync(...)`는 `NotificationsService`, `NOTIFICATIONS`, `NOTIFICATION_CHANNELS`를 global provider로 export합니다. 애플리케이션 서비스는 fluo의 class-level `@Inject(...)` decorator로 의존성을 선언해야 standard-decorator DI container가 parameter decorator 없이 서비스를 resolve할 수 있습니다.
		`NotificationsModule.forRoot(...)`와 `NotificationsModule.forRootAsync(...)`는 기본적으로 `NotificationsService`, `NOTIFICATIONS`, `NOTIFICATION_CHANNELS`를 global provider로 export합니다. 이 provider들이 notifications module을 import한 module 안에서만 보이도록 유지하려면 `global: false`를 설정합니다. 애플리케이션 서비스는 fluo의 class-level `@Inject(...)` decorator로 의존성을 선언해야 standard-decorator DI container가 parameter decorator 없이 서비스를 resolve할 수 있습니다.

		@@ -212,2 +212,3 @@ ## 일반적인 패턴
		상태 snapshot은 platform diagnostics를 위해 `operationMode`, dependency diagnostics, ownership, readiness, health 필드를 포함합니다.
		Queue adapter가 구성되면 `details.dependencies`에 `notifications.queue-adapter`가 포함되고, lifecycle event가 event publisher를 통해 발행되면 `notifications.event-publisher`가 포함됩니다. 이러한 선택적 통합은 `ownership.externallyManaged: true`로 표시되지만, foundation 패키지가 concrete queue 또는 event-bus 리소스를 닫지 않으므로 `ownsResources: false`를 유지합니다.

		@@ -214,0 +215,0 @@ ## 관련 패키지

+2

-1

README.md

		@@ -92,3 +92,3 @@ # @fluojs/notifications

		`NotificationsModule.forRoot(...)` and `NotificationsModule.forRootAsync(...)` export `NotificationsService`, `NOTIFICATIONS`, and `NOTIFICATION_CHANNELS` as global providers. Application services should declare dependencies with fluo's class-level `@Inject(...)` decorator so the standard-decorator DI container can resolve the service without parameter decorators.
		`NotificationsModule.forRoot(...)` and `NotificationsModule.forRootAsync(...)` export `NotificationsService`, `NOTIFICATIONS`, and `NOTIFICATION_CHANNELS` as global providers by default. Set `global: false` when these providers should stay visible only to the module that imports the notifications module. Application services should declare dependencies with fluo's class-level `@Inject(...)` decorator so the standard-decorator DI container can resolve the service without parameter decorators.

		@@ -212,2 +212,3 @@ ## Common Patterns
		Status snapshots include `operationMode`, dependency diagnostics, ownership, readiness, and health fields for platform diagnostics.
		When a queue adapter is configured, `details.dependencies` includes `notifications.queue-adapter`; when lifecycle events are published through an event publisher, it includes `notifications.event-publisher`. Those optional integrations mark `ownership.externallyManaged: true` while the foundation package still reports `ownsResources: false` because it does not close concrete queue or event-bus resources.

		@@ -214,0 +215,0 @@ ## Related Packages

@fluojs/notifications - npm Package Compare versions

Improved metrics

Dependency changes