refactor: align event mapper and client lifecycle #463
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Related issue: #____
What changed?
GenericEventand refreshed supporting helpers so signing and dispatch use the clearerserializedEventCacheaccessors.EventJsonMapperto own the shared Jackson configuration and swapped previousIEventconstants and call sites to the new utility for cleaner dependencies.NostrSpringWebSocketClientwith an initialization-on-demand holder to remove volatile state while keeping lazy initialization semantics.NostrSpringWebSocketClientconstructors so default and note-service instances no longer fail null checks when delegating.BREAKING
None.
Review focus
EventJsonMapperwiring covers all formerIEvent.MAPPER_BLACKBIRDusages without leaving stray imports.NostrSpringWebSocketClientstill satisfies existing entry points.Checklist
Testing
mvn -q verify(fails: xyz.tcheeric:nostr-java-bom:1.1.1 missing from Maven Central)https://chatgpt.com/codex/tasks/task_b_68e383c7988483319301f67a61c92ce6