Hi Sean,
Sorry for the delay on the answer. Yes, that's a good spot. Another thing I
usually do is to put a halt in FLSerialization >> run. Just after
#analysisStep for example, and then inspect the local variables.
Also, if you want to understand WHY an object is getting in, then you can
also ha
I had an object graph that was pulling in all sorts of unrelated classes when
serialized with Fuel. I was trying to find the offending object, and came up
with the following:
```
(FLAnalyzer newDefault analysisFor: root) clusterization globalsBucket
```
This worked, but I was wondering if that's "
