From 5acdc975398000f38dec68bc144abb361d9d6ef1 Mon Sep 17 00:00:00 2001
From: Bart Debersaques <Bart.Debersaques@mail.qqdatafruits.be>
Date: Thu, 29 Jan 2026 11:28:45 +0100
Subject: [PATCH] fix: proposal to solve "FamixUMLRoassalBackend does not show
 all relevant associations when displaying CoastersCollector example" as
 illustrated in moosetechnology#1070

---
 .../FamixUMLRoassalDescriptor.class.st                 | 10 ++++++++++
 1 file changed, 10 insertions(+)

diff --git a/src/Famix-UMLDocumentor/FamixUMLRoassalDescriptor.class.st b/src/Famix-UMLDocumentor/FamixUMLRoassalDescriptor.class.st
index f4cb59e60..caf4f29f6 100644
--- a/src/Famix-UMLDocumentor/FamixUMLRoassalDescriptor.class.st
+++ b/src/Famix-UMLDocumentor/FamixUMLRoassalDescriptor.class.st
@@ -38,6 +38,16 @@ FamixUMLRoassalDescriptor >> aggregations [
 			(self umlClassNamed: aggreg source) -> (self umlClassNamed: aggreg target) ])
 ]
 
+{ #category : 'accessing' }
+FamixUMLRoassalDescriptor >> associations [ 
+
+	^(umlModel
+		select: [ :umlEntity | umlEntity class = FamixUMLAssociation and: [ umlEntity aggregation = #off ]]
+		thenCollect: [ :use |
+			(self umlClassNamed: use target) -> (self umlClassNamed: use source) ])
+
+]
+
 { #category : 'accessing' }
 FamixUMLRoassalDescriptor >> compositions [