[alexanderlinne]

The exporter uses a slice's name as its PlantUML id, but not every name is a valid one. PlantUML rejects *, +, `, < and
> in an id,

[Inner] as App.Outer+Inner syntax error
Container(App.Outer+Inner, Inner) error box instead of a container

and slice names can contain them: SlicedBy names slices after type names such as Outer+Inner or List`1, and a hand-built SliceIdentifier can be called anything. Only the flat, non-C4 form [App.Outer+Inner] happens to work, because it declares no id.

No character a namespace cannot contain works in their place: of -$#~:%@!^ only $ is accepted, and only outside C4. So give such a slice an id of its own when the diagram is rendered: its name with every character other than letters, digits, _ and . replaced by _, suffixed until it clashes with no other name in the diagram, and point the dependencies at it. The name stays the label, and a slice whose name is a valid id keeps it, so no existing diagram changes. The ids are assigned when rendering because the exporter matches slices and dependencies by name throughout.

A * at the start of a label is read as a list bullet and dropped, so it is escaped as ~*.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.32%. Comparing base (192657e) to head (12209be).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #510      +/-   ##
==========================================
+ Coverage   86.25%   86.32%   +0.06%     
==========================================
  Files         260      260              
  Lines       12500    12563      +63     
  Branches     1218     1225       +7     
==========================================
+ Hits        10782    10845      +63     
  Misses       1379     1379              
  Partials      339      339              

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.