modular-architecture.md: show SLF4J and JSpecify as dependencies of base

This is just a informational change. In the interest of keeping
the diagram simple, I have not been showing multiple links to minor direct
dependencies. But this change chooses to display SLF4J & JSpecify as
direct dependencies of `base`. This makes it more clear that
`base`, `core` and `wallet` all will depend on them. The diagram
still "lies" a little bit in not showing that they are also direct
dependencies, but I think that is an acceptable tradeoff for a diagram
that is easier to read.
This commit is contained in:
Sean Gilligan 2025-02-27 10:06:59 -08:00 committed by Andreas Schildbach
parent 0e648bcba2
commit e7545cafe3

View file

@ -87,8 +87,8 @@ flowchart TD
SECPBC --> BC[Bouncy Castle] SECPBC --> BC[Bouncy Castle]
SECPFFM --> SECPC[libsecp256k1] SECPFFM --> SECPC[libsecp256k1]
CORE --> P[ProtoBuf] CORE --> P[ProtoBuf]
CORE .-> S[slf4j] BASE .-> S[slf4j]
CORE .-> JS[JSpecify] BASE .-> JS[JSpecify]
classDef external fill:#999; classDef external fill:#999;
class G,S,JS,BC,SECPC,P external; class G,S,JS,BC,SECPC,P external;
@ -123,9 +123,9 @@ flowchart TD
CO[o.b.core] --> CR[o.b.crypto] CO[o.b.core] --> CR[o.b.crypto]
end end
CORE --> BASE CORE --> BASE
CORE .-> S[slf4j]
CORE .-> JS[JSpecify]
CORE --> SECP CORE --> SECP
BASE .-> S[slf4j]
BASE .-> JS[JSpecify]
SECP[secp-api] .-> SECPFFM[secp-ffm] SECP[secp-api] .-> SECPFFM[secp-ffm]
SECP .-> SECPBOUNCY[secp-bouncy] SECP .-> SECPBOUNCY[secp-bouncy]
SECPBOUNCY .-> BC[Bouncy Castle] SECPBOUNCY .-> BC[Bouncy Castle]