Skip to content

Consider enforcing a consistent output row ordering in epi_slide, epix_slide #323

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
Open
brookslogan opened this issue May 31, 2023 · 2 comments
Open

Consider enforcing a consistent output row ordering in epi_slide, epix_slide #323

brookslogan opened this issue May 31, 2023 · 2 comments
Labels
op-semantics Operational semantics; many potentially breaking changes here P3 very low priority

Comments

@brookslogan
Copy link
Contributor

brookslogan commented May 31, 2023 •
edited
Loading

Currently, epi_slide probably arranges by group vars & time_value, while epix_slide likely arranges by (ref_)time_value & group vars.
@brookslogan brookslogan added P3 very low priority op-semantics Operational semantics; many potentially breaking changes here labels May 31, 2023
@brookslogan
Copy link
Contributor Author

Not sure we want these to match between epi_slide and epix_slide. In the slide improvements pass there is the lingering question of whether we should actually reorder the columns to better "match" the different row ordering there.

@brookslogan brookslogan reopened this Oct 14, 2024
@brookslogan
Copy link
Contributor Author

Not sure if the column ordering was migrated to another issue from this checklist. Leaving open for now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
op-semantics Operational semantics; many potentially breaking changes here P3 very low priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@brookslogan