Motivation
centralize development and test environment
Dreams 🔮
- remove configurations for linters from individual packages
- remove
run-tests.sh from individual packages
- have a centralized place where linter configuration and test setup can be collected
- make github tests and local tests + development configuration collected from same place
- pyproject.toml as single configuration for package build (i.e.
MANIFEST.in, build-backend, etc.)
- pyproject.toml contains only package build information (i.e. not config for Babel, linter, etc. This would be centralized)
- configuration for babel, tests, linter on centralized place
- translation configuration on centralized place
interfaces
invenio start tests command. (invenio run tests is not possible, invenio run starts a development server)
- one package on inveniosoftware which contains all configuration, javascript, python, linters, translations etc
possible tools and technologies and concepts
Next steps
- Move config to
pyproject.toml
- Test out the following tools for a centralized config workflow (in this order):
Motivation
centralize development and test environment
Dreams 🔮
run-tests.shfrom individual packagesMANIFEST.in, build-backend, etc.)interfaces
invenio start testscommand. (invenio run testsis not possible,invenio runstarts a development server)possible tools and technologies and concepts
Next steps
pyproject.tomlinvenio-cli tests