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

feat(json): Warn on missing RECOMMENDED metadata #2027

Merged
merged 2 commits into from
Jul 29, 2024

Conversation

effigies
Copy link
Collaborator

This dramatically increases the number of warnings emitted, since BIDS has been very liberal with its RECOMMENDATIONS.

The alternative is to go add issues to all of the sidecar fields that previously warned.

Copy link

codecov bot commented Jul 29, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.35%. Comparing base (56734ab) to head (297c2e8).

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #2027      +/-   ##
==========================================
+ Coverage   85.75%   87.35%   +1.59%     
==========================================
  Files          91      132      +41     
  Lines        3785     6325    +2540     
  Branches     1218     1526     +308     
==========================================
+ Hits         3246     5525    +2279     
- Misses        453      709     +256     
- Partials       86       91       +5     

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

@rwblair
Copy link
Member

rwblair commented Jul 29, 2024

People seem to ignore warnings as is, but not reporting them is against the spirit of BIDS. I'm neutral either way.

@rwblair rwblair merged commit 384fe6f into bids-standard:master Jul 29, 2024
33 checks passed
@effigies effigies deleted the feat/warn-missing-recommended branch July 29, 2024 18:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants