Skip to content

Define AfterFind behavior for Eager connections #476

@aeneasr

Description

@aeneasr

Description

At the moment, AfterFind is being executed before fetching any other relations (using Eager()). This is not documented very well and maybe even unexpected.

Steps to Reproduce the Problem

Have a model with at least one has_many relation defined and a value receiver AfterFind().

Expected Behavior

Three options:

  1. Document this behavior as a limitation
  2. Add another method such as AfterFindEager
  3. Run AfterFind() after fetching relations if an eager connection is made.

Metadata

Metadata

Assignees

No one assigned

    Labels

    f: associationsthe associations feature in pops: triageSome tests need to be run to confirm the issue

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions