Skip to content

Comments

Loading different attributes#76

Merged
leoguignard merged 6 commits intov2.xfrom
Loading-different-attributes
Jun 25, 2025
Merged

Loading different attributes#76
leoguignard merged 6 commits intov2.xfrom
Loading-different-attributes

Conversation

@BadPrograms
Copy link
Collaborator

We only allow dict properties to be loaded. Some properties that are not dict should not be loaded, while others are important like the time resolution. Should we change the loader or add each important non dict attribute manually?

@codecov
Copy link

codecov bot commented Jun 23, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.77%. Comparing base (bbe1e2f) to head (78174b4).
Report is 7 commits behind head on v2.x.

Additional details and impacted files
@@           Coverage Diff           @@
##             v2.x      #76   +/-   ##
=======================================
  Coverage   96.77%   96.77%           
=======================================
  Files           2        2           
  Lines         341      341           
  Branches       17       17           
=======================================
  Hits          330      330           
  Misses          6        6           
  Partials        5        5           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@@ -1,4 +1,4 @@
__version__ = "2.0.1"
__version__ = "2.1.1"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is that really a minor change and not a patch?

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh indeed it should be a patch

prop_name: prop
for prop_name, prop in lT.__dict__.items()
if isinstance(prop, dict)
if (isinstance(prop, dict) or prop_name == "_time_resolution")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we think of possible other properties?
Probably there is no strong reason for only allowing dictionary properties.

That being said, we only want lineage Tree properties and not other "weird" things/dunder properties and so on.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is for older files only v1.x, so I don't think we should overthink that. There is only one property we used in this version: time_resolution.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, it is marginally impacting anyway ...

Copy link
Member

@leoguignard leoguignard left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you still bump as patch before merging?

prop_name: prop
for prop_name, prop in lT.__dict__.items()
if isinstance(prop, dict)
if (isinstance(prop, dict) or prop_name == "_time_resolution")
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sure, it is marginally impacting anyway ...

@leoguignard leoguignard merged commit 278011f into v2.x Jun 25, 2025
3 checks passed
@BadPrograms BadPrograms deleted the Loading-different-attributes branch July 1, 2025 08:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants