Avoid circular dependencies

[Firesphere]

When I have a circular relation, e.g. every object in the database ends up being dumped out.

Did I use the limiting via exclude? Yes.

But it still dumps out everything.

I would like a feature that would limit the dependency circle to 1.

E.g.
Location => City(1) => Locations(1) => City(Already exists)

Currently, because in the above, a City has a lot of locations, every location gets included, I wish it was limited to 1.

I'm very sure this is not explained clearly, but I hope it is clear enough to get the picture :D

[chrispenny]

Thanks for raising this :) Exiting to see someone's using the module!

Probably the relevant PR where this behaviour changed:
#21

I put the question out there, but didn't get any feedback - so I went with "traverse all valid relationships until they run out".

One solution that might(?) work for you right now is excluding the relationship for Locations::$City. EG:

App\Models\Locations:
  excluded_fixture_relationships:
    - City (the relationship name)

I think it would be possible to add support for stopping when we detect looping dependencies. In all honesty, I'm not sure when I'll have time available to work on it though.

[Firesphere]

That's what I tried, but I sadly still get the full list. Even when trying to apply this on a single relationship...

I think something might be going wrong in there.

However! I think it would be good to add an option to limit the depth, because fixtures are usually only used for tests, there's no need for recursively going through every potential option that might come from a production database.

Other than that, I do like it, this does make fixtures generally easier! :D