Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rethink / -design Path #82

Open
gammelalf opened this issue Feb 17, 2025 · 0 comments
Open

Rethink / -design Path #82

gammelalf opened this issue Feb 17, 2025 · 0 comments

Comments

@gammelalf
Copy link
Member

Currently Path represents a "path of joins" i.e. a step always corresponded to a join.

This means to properly support FieldProxy, mcf would have to do a lot of weird generic workarounds (if even possible)

A better solution might be to rethink what a Path represents. One idea:
A Path simply corresponds to the chain of field accesses used to construct it:

User.groups.owner.name
\_______________/ \__/
      path       field
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant