-
Notifications
You must be signed in to change notification settings - Fork 370
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
Empty column tracker and new dataframe APIs on top #7677
Conversation
b3cde2b
to
11f9156
Compare
11f9156
to
f5b5d3c
Compare
f5b5d3c
to
7ba19c7
Compare
|
||
/// Whether this column represents an indicator component. | ||
pub is_indicator: bool, | ||
|
||
/// Whether this column represents a [`Clear`]-related components. | ||
/// | ||
/// [`Clear`]: re_types_core::archetypes::Clear | ||
pub is_tombstone: bool, | ||
|
||
/// Whether this column contains either no data or only contains null and/or empty values (`[]`). | ||
pub is_semantically_empty: bool, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we just expose ColumnMetadata
here directly?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Eeeh, as this is the heart of the API, I'd prefer to keep it flat, simple to inspect and simple to build by hand.
Before:
After:
Of course with static data this still looks pretty weird in many cases, such as shown in this screenshot,
But that's a job for the upcoming #7668.
Checklist
main
build: rerun.io/viewernightly
build: rerun.io/viewerCHANGELOG.md
and the migration guideTo run all checks from
main
, comment on the PR with@rerun-bot full-check
.