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

Dataflow debugger #220

Open
tuner opened this issue Jan 11, 2024 · 0 comments
Open

Dataflow debugger #220

tuner opened this issue Jan 11, 2024 · 0 comments
Labels
core Related to the Core package enhancement New feature or request UX Related to user experience. Usability, visual style, etc.

Comments

@tuner
Copy link
Member

tuner commented Jan 11, 2024

If no mark instances are shown in the visualization, it's a bit difficult to figure out what's the reason. The main culprit is that when an undefined field is accessed, it's interpreted as a null value, which is currently not an error. This could be mitigated by tracking the columns that the data objects should have and raise an error when an accessor tries to access a nonexistent column. However, there are also other reasons why no data is shown.

Anyway, some sort of tool to visualize the data flow and inspect random data objects (like the first/last) would make debugging much easier. Vega editor has a really fancy one, but something much simpler would be enough as GenomeSpy's data flow model is much simpler.

@tuner tuner added enhancement New feature or request core Related to the Core package UX Related to user experience. Usability, visual style, etc. labels Jan 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Related to the Core package enhancement New feature or request UX Related to user experience. Usability, visual style, etc.
Projects
None yet
Development

No branches or pull requests

1 participant