Component Diagram Interfaces

[ziidonato]

Proposal

Problem

• There is no real support for lollipop/ball & socket interfaces. Common in component diagrams, they look like this:

You can see as an example, send & receive email are interfaces, with the email inbox being the "pusher" and the email management component being the receiver.

Currently, MermaidJS has the ball (or lollipop, as you call it), but no socket. I don't believe this is sufficient.

Solution

• Please integrate the socket, so making these components in mermaid can be a lot smoother.
• Speaking of which, there doesn't seem to be any official support for component diagrams. Is it assumed that they are the same as/an extension of class diagrams? That's fair, but please integrate the full functionality of a component diagram (such as nested components, ports, those

Example

component Source {
     ProcessArguments:
     ArgProcessor -o)- Client

     ProcessResponse
     Client -o)- ResponseProcessor
}

component DataCruncher {
     ParseConfig:
     ConfigParser -(o- ByteReader
}

component Publisher {
     Broadcast:
     DataProcessor -(o- Broadcaster
}

FetchData:
DataCruncher -o)- Source

PublishData:
PublishData -o) Source

Results in this:

Screenshots

No response