Skip to content

Add V2 design for parser protocol and open_virtual_dataset #598

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

Closed
wants to merge 9 commits into from

Conversation

maxrjones
Copy link
Member

Following design structure in #568

Builds on changes in #595, which should be merged first.

Closes #553
Closes #245

Copy link

codecov bot commented May 16, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 89.57%. Comparing base (7b0083e) to head (c3a5c86).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #598      +/-   ##
===========================================
+ Coverage    89.34%   89.57%   +0.23%     
===========================================
  Files           34       37       +3     
  Lines         1943     1986      +43     
===========================================
+ Hits          1736     1779      +43     
  Misses         207      207              
Files with missing lines Coverage Δ
virtualizarr/manifests/store.py 92.48% <100.00%> (+0.46%) ⬆️
virtualizarr/testing/utils.py 100.00% <100.00%> (ø)
virtualizarr/v2/api.py 100.00% <100.00%> (ø)
virtualizarr/v2/protocols.py 100.00% <100.00%> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Member

Choose a reason for hiding this comment

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

Why do we need a v2 namespace? Shouldn't we just be directly replacing the functions we already have?

Copy link
Member Author

Choose a reason for hiding this comment

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

The purpose is to allow updating parsers incrementally, but no worries if you prefer to do it all in one go with Sean's branch.

Copy link
Member

Choose a reason for hiding this comment

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

I would prefer to do it all in one go if we can!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants