Skip to content

Conversation

@brokkoli71
Copy link
Member

@brokkoli71 brokkoli71 commented Feb 15, 2025

TODO:

  • Add unit tests and/or doctests in docstrings
  • Add docstrings and API docs for any new/modified user-facing classes and functions
  • New/modified features documented in docs/user-guide/*.rst
  • Changes documented as a new file in changes/
  • GitHub Actions have all passed
  • Test coverage is 100% (Codecov passes)

@github-actions github-actions bot added the needs release notes Automatically applied to PRs which haven't added release notes label Feb 15, 2025
@github-actions github-actions bot removed the needs release notes Automatically applied to PRs which haven't added release notes label Feb 15, 2025
@brokkoli71 brokkoli71 marked this pull request as ready for review February 18, 2025 12:19
@brokkoli71 brokkoli71 requested a review from normanrz May 13, 2025 11:58
@d-v-b
Copy link
Contributor

d-v-b commented May 13, 2025

i think this is a good idea, and for codecs that have simple defaults (blosc and gzip and most conventional compressors), it's very user-friendly. but IMO we need to give users a very clear error when they use a string name for a codec that takes required parameters.

@brokkoli71 brokkoli71 requested a review from d-v-b May 27, 2025 13:24
@brokkoli71
Copy link
Member Author

@d-v-b what do you think of the updated error messages?

# Conflicts:
#	tests/test_array.py
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.

Array creation should take strings for filters, serializer, compressors

3 participants