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.

Sign up for GitHub

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

Jump to bottom

Explore feasibility of coerced variable refactor #2764

Closed
dondonz opened this issue Mar 18, 2022 · 0 comments
Closed

Explore feasibility of coerced variable refactor #2764

dondonz opened this issue Mar 18, 2022 · 0 comments

Comments

@dondonz
Copy link
Member

dondonz commented Mar 18, 2022

Explore whether it's feasible/useful to introduce holders for coerced and uncoerced variable values.

For example, there are two QueryTraverser constructors, one which takes coerced variables and the other does not. It could be clearer where we coerced variables, and where we don't. Might also help with more refactoring down the track.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@dondonz