Generated from aind-library-template
Project description
aind-metadata-mapper
Repository to contain code that will parse source files into aind-data-schema models.
Usage
Installation
To use the software, in the root directory, run
pip install -e .[all]
It's possible to install just a small subset of dependencies. For example,
pip install -e .[bergamo]
To develop the code, run
pip install -e .[dev]
Contributing
Linters and testing
There are several libraries used to run linters, check documentation, and run tests.
- Please test your changes using the coverage library, which will run the tests and log a coverage report:
coverage run -m unittest discover && coverage report
- Use interrogate to check that modules, methods, etc. have been documented thoroughly:
interrogate .
- Use flake8 to check that code is up to standards (no unused imports, etc.):
flake8 .
- Use black to automatically format the code into PEP standards:
black .
- Use isort to automatically sort import statements:
isort .
Pull requests
For internal members, please create a branch. For external members, please fork the repository and open a pull request from the fork. We'll primarily use Angular style for commit messages. Roughly, they should follow the pattern:
<type>(<scope>): <short summary>
where scope (optional) describes the packages affected by the code changes and type (mandatory) is one of:
- build: Changes that affect build tools or external dependencies (example scopes: pyproject.toml, setup.py)
- ci: Changes to our CI configuration files and scripts (examples: .github/workflows/ci.yml)
- docs: Documentation only changes
- feat: A new feature
- fix: A bugfix
- perf: A code change that improves performance
- refactor: A code change that neither fixes a bug nor adds a feature
- test: Adding missing tests or correcting existing tests
Semantic Release
The table below, from semantic release, shows which commit message gets you which release type when semantic-release
runs (using the default configuration):
Commit message | Release type |
---|---|
fix(pencil): stop graphite breaking when too much pressure applied |
|
feat(pencil): add 'graphiteWidth' option |
|
perf(pencil): remove graphiteWidth option BREAKING CHANGE: The graphiteWidth option has been removed. The default graphite width of 10mm is always used for performance reasons. |
(Note that the BREAKING CHANGE: token must be in the footer of the commit) |
Documentation
To generate the rst files source files for documentation, run
sphinx-apidoc -o doc_template/source/ src
Then to create the documentation HTML files, run
sphinx-build -b html doc_template/source/ doc_template/build/html
More info on sphinx installation can be found here.
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Hashes for aind_metadata_mapper-0.16.1.tar.gz
Algorithm | Hash digest | |
---|---|---|
SHA256 | 33b29387400de38af81e22f57a1e74a88f6b2244c97ef8faf2aa317e86088af7 |
|
MD5 | aa1d4df9c5a5efeb3985415e23daa231 |
|
BLAKE2b-256 | 13f503db9cd6ffe710534701093813a4e984128e46de535fedaf3a9d0c2b40e5 |
Hashes for aind_metadata_mapper-0.16.1-py3-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 0b32c8a4d4d73a094d27d0a92d22b4a46a5f64b4fc9405fcec4b93bf3b1ec98a |
|
MD5 | 2b97ca1bc3a37b448b43c890e28301d8 |
|
BLAKE2b-256 | 9f52e25ec5d032a4ccbf6a74969f48bad50d47ee25591863ecd0af62567c8e11 |