Alexander Tømmerås

Oh, this is the auto-eager loading kicking in, which uses the `$load` properties to find all nested relations. If you don’t use the an includeXx method, the package will assume...

The idea has been to mask out Fractal (with the exception of the serializers, which already kind of are decoupled) from the point of view of the user. Almost all...

Hmm, I've been tinkering a bit with this and as long as you use the `$load` property with transformer mappings, I can get things working fine. However, this issue is...

The problem is that I don't yet have the related models because I need to verify they're allowed through their transformers before eager loading them. Which means the explicit binding...

> Where you talking about this scenario I depicted? Yes, indeed! You're right though that with conditional attributes this might not be too common, and it might be a bit...

Oh, and yes, I agree with you about the security aspect. I'll get that fixed :)

I've read this thread a couple times now, but not exactly sure what the exact problem here was again. Can you check if this is solved with the latest release?

Yeah, would be nice you could open an issue on the morphable feature, not sure I fully understand how it should work. Also, with v3 you now map transformers on...

The code for fetching a relationship from a model is located here: https://github.com/flugger/laravel-responder/blob/master/src/Transformers/Concerns/HasRelationships.php#L220. As you can see it resolves the relation as if it was a model attribute and should...

> The only problems I can see are when a model has an attribute with a snake_cased name which corresponds to the camel cased name of a relation and the...