Skip to main content

Development

What counts as development in this repo​

This repository owns a LiteRT / TensorFlow Lite .tflite converter stage inside the wider MLIA pipeline. Most changes here affect conversion behaviour, plugin registration, and the expectations of the downstream backends that consume converted artifacts.

Local setup​

Use uv to create and sync the development environment:

uv sync --group dev

Common commands​

Run the full test suite:

uv run pytest --no-success-flaky-report tests/

Run the quick CI-like subset:

uv run pytest --no-success-flaky-report -m "not slow" tests/

Run linting and repository checks:

uv run pre-commit run --all-files

Build a wheel:

uv build --wheel

What usually changes together​

When you change conversion behaviour, also review:

  • Plugin registration and discovery tests.
  • Conversion-specific tests and fixtures.
  • Assumptions made by downstream backends that consume TOSA-oriented artifacts.
  • Docs that describe the converter as part of a larger pipeline.

Good review questions​

Before you consider a change complete, ask:

  • Does the converter still register correctly inside a wider MLIA install?
  • Do the end-to-end examples still describe the real pipeline?
  • Is the failure mode understandable when conversion breaks?
  • Did the change alter the expected downstream artifact shape?

Documentation expectations​

Document this repo as a pipeline component, not as a standalone CLI product. Keep examples focused on end-to-end MLIA runs that include the converter.