Ports on parts do not group below owning block

[mikekidner]

Describe the bug

As discussed ports do not group beneath the owning block, if created on the part. Also, ports created on a block are not available to use on the part.

To Reproduce

Steps to reproduce the behavior:

1. Create a blocks B1 , B2, B3, with ports on B2 and B3. See how they are grouped beneath the blocks in the model.

2. Create an IBD for B1

See how the ports are not available to use on the diagram

3. Add a port to a part in the IBD. See how it appears at the top level of the model, not under the owning block

Expected behavior

When adding ports to a block or it's corresponding part, it is expected that the port nests beneath the block.
If a port exists on a block, it should exist on the corresponding part.

OS

• Linux (Please put in notes the specific distro)
• macOS
• Windows

Version

Version of Gaphor: 2.18.1

Additional information

Add any other context about the problem here.

[amolenaar]

Thanks @mikekidner, I can reproduce this issue.

[amolenaar]

The missing piece is here: https://github.com/gaphor/gaphor/blob/main/gaphor/SysML/blocks/connectors.py#L39-L40.

Is a Property actually allowed to have Ports? Port is a subtype of Property.

If so, what would the relation be? For a ProxyPort on a Property? Property.subsettedProperty?

[mikekidner]

I think that placing a port on a part should be interpreted as adding a port property to the owning block,
So when dropping a port onto a part in a diagram, it would have to reference the owning block.

To do nested ports, a port would have to have port properties. So ports, may need to be realised as properties that can own properties, as you suggest.

[amolenaar]

I check Visual Paradigm, and there the port is attached to the type of the property:

This would mean that types have to be fixed (currently type is a pretty free form text field).

[mikekidner]

This is great. Thanks.