Explore possibility of using Traits to drop the requirement to subclass

[sebastianconcept]

Can the Mapless behavior be injected as a Trait to an arbitrary class?

https://github.com/pharo-open-documentation/pharo-wiki/blob/master/General/Traits.md

[sebastianconcept]

See stateful traits

Trait named: #Mapless
	uses: {}
	slots: { #data }
	package: 'Mapless-Core'

[sebastianconcept]

This was key:

anObject class isComposedBy: MaplessBehavior

instead of

anObject isKindOf: Mapless

Here

"protocol: #actions"

asStorable: anObject
	^ anObject isCollection
		ifTrue: [ anObject class = OrderedJsonObject
				ifTrue: [ (JsonObject fromAssociations: anObject associations)
						collect: [ :e | resolver maplessAsStorable: e in: self ] ]
				ifFalse: [ anObject collect: [ :e | self asStorable: e ] ] ]
		ifFalse: [ anObject class = MaplessReference
				ifFalse: [ (anObject class isComposedBy: MaplessBehavior )
						ifTrue: [ (resolver asMaplessReferenceIn: anObject in: self)
								asJsonObjectIn: self ]
						ifFalse: [ anObject ] ]
				ifTrue: [ (anObject hasModel and: [ anObject data id isNil ])
						ifFalse: [ resolver maplessReferenceAsJsonObject: anObject in: self ]
						ifTrue: [ MaplessUnsavedSubmodel
								signal:
									'This sub model is unsaved. You need to save all sub models before saving a composed model' ] ] ]

cc/ @paulwilke

[paulwilke]

@sebastianconcept thanks for the heads up. I wanted to check out the code&tests but I don't see them in the develop branch. Where should I look please?

[sebastianconcept]

Oh, sorry I noticed this message only now @paulwilke !

With a Pharo 11, this is what I get:

I was hoping to see you creating a branch out of develop (with issue #147) and push there whatever changes are made to the image when applying the .st file you sent me:

MaplessBehavior.st.zip

Once you push that, things will break but I'll add the fixes and tests.

Sounds good?