We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Path
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)
FieldProxy
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
The text was updated successfully, but these errors were encountered:
No branches or pull requests
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:The text was updated successfully, but these errors were encountered: