In my opinion the #fuelAccept: for the meta description object should be overridden and there the behaviour for problematic references should be defined. Roberto, what references does your meta object hold on to? Max On 28.10.2013, at 22:16, Martin Dias <tinchodias@gmail.com> wrote:
On Mon, Oct 28, 2013 at 5:13 PM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: The idea is that I have an object (a session) which has meta data (time, duration, author) and some other object inside.
I want that Fuel serializes just that object and not pointes to other object, globals and what not.
This causes me a lot of troubles, moreover it makes the fuel file bigger than the optimumâ¦
Still there is something that I don't understand in your problem. If you just prune the graph, what your objects represent (conceptually) can be lost. Did you pick one of your problematic "session objects" are explored it until find how the unwanted block closures are referenced? I mean, fuel doesn't invent the unwanted closures magically, you are saying to fuel to serialize the graph with the unwanted objects already there.
Cheers, R
On Oct 28, 2013, at 4:57 PM, Martin Dias <tinchodias@gmail.com> wrote:
On Mon, Oct 28, 2013 at 4:47 PM, roberto.minelli@usi.ch <roberto.minelli@usi.ch> wrote: Thanks,
On Oct 28, 2013, at 4:36 PM, Martin Dias <tinchodias@gmail.com> wrote:
Currently there is no such option.
Maybe it is something which is needed, what do you think?
The idea is that, if you serialize:
a -> b -> c
fuel actually would encode:
a -> b -> nil
that?