silx.io.nxdata: Updated get_default
to be more permissive and follow @default
recursively
#3662
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR changes behavior of
silx.io.nxdata.get_default
.The search of
@default
NXdata
now recursively follows@default
.It also stop checking
NX_class
along the way (i.e.,NXroot/NXentry/NXdata
) and only checks forNX_class="NXdata"
to find theNXdata
group.I'm wondering if the
silx.io.nxdata
functions:is_group_with_default_NXdata
,is_NXentry_with_default_NXdata
,is_NXroot_with_default_NXdata
that were used byget_default
are used anywhere (they're no longer used in silx), I'm tempted to deprecate them...It still needs a bit of testing.
closes #3605