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

Input order should match variable availability order when possible #1077

Open
t3kt opened this issue May 14, 2023 · 0 comments
Open

Input order should match variable availability order when possible #1077

t3kt opened this issue May 14, 2023 · 0 comments
Labels
cleanup

Comments

@t3kt
Copy link
Owner

t3kt commented May 14, 2023 •
edited
Loading

In general, execution order for field inputs should be top to bottom, allowing lower inputs to depend on higher ones.
The main exception to this is for transform filters where the first input is generally executed last (after transforms are applied to coordinates)
@t3kt t3kt added the cleanup label May 14, 2023
@t3kt t3kt added this to the 0.34 milestone May 14, 2023
t3kt added a commit that referenced this issue May 20, 2023
@t3kt
reorder inputs to match variable availability
e1e802b 
see #1077
t3kt added a commit that referenced this issue May 24, 2023
@t3kt
variable settings and input reordering
88cf60c 
see #1077
t3kt added a commit that referenced this issue May 30, 2023
@t3kt
input ordering and variable settings
b63adf6 
see #1077
t3kt added a commit that referenced this issue Jun 2, 2023
@t3kt
input order and variable settings
b921b78 
see #1077
t3kt added a commit that referenced this issue Jun 2, 2023
@t3kt
input order and variable settings
d6b4446 
see #1077
@t3kt t3kt removed this from the 0.34 milestone Jun 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
cleanup
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@t3kt