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

Custom fields confuse the unused Joins list #110

Open
ajcrutch opened this issue Sep 9, 2024 · 0 comments
Open

Custom fields confuse the unused Joins list #110

ajcrutch opened this issue Sep 9, 2024 · 0 comments

Comments

@ajcrutch
Copy link

ajcrutch commented Sep 9, 2024

If a custom field matches the name of a join, it could mistakenly register that join as used. This is because custom fields are expressed without a view scoping (viewname.fieldname) and are simply listed as their field name (fieldname). So if that fieldname matches a real join in the explore, it will interfere with Henry.

In the fetcher.py module

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