Skip to content

Add Lemonfox transcription provider#23

Closed
DYSfu wants to merge 2 commits into
nibzard:mainfrom
DYSfu:add-lemonfox-transcription
Closed

Add Lemonfox transcription provider#23
DYSfu wants to merge 2 commits into
nibzard:mainfrom
DYSfu:add-lemonfox-transcription

Conversation

@DYSfu
Copy link
Copy Markdown

@DYSfu DYSfu commented May 20, 2026

Summary

  • add a Lemonfox Speech-to-Text provider available through --api lemonfox
  • document the required Lemonfox environment variables and usage example
  • add mocked unit coverage for the OpenAI-compatible transcription request and CLI routing

Validation

  • . .venv/bin/activate && PYTHONPATH=src python -m unittest discover -s tests -v
  • . .venv/bin/activate && PYTHONPATH=src python -m py_compile src/sapat/script.py src/sapat/transcription/lemonfox.py tests/test_lemonfox_transcription.py tests/test_script.py
  • . .venv/bin/activate && PYTHONPATH=src python -m sapat.script --help
  • git diff --check

Related Daytona content bounty: daytonaio/content#13

@DYSfu
Copy link
Copy Markdown
Author

DYSfu commented May 21, 2026

Pushed a follow-up fix in decb020 after rechecking the PR locally.

The CLI now imports only the selected transcription provider, so Lemonfox routing and tests no longer require unrelated provider SDKs to be importable at module import time.

Validation:

  • PYTHONPATH=src python -m unittest discover -s tests -v
  • PYTHONPATH=src python -m py_compile src/sapat/script.py src/sapat/transcription/lemonfox.py tests/test_lemonfox_transcription.py tests/test_script.py
  • PYTHONPATH=src python -m sapat.script --help
  • git diff --check

@nibzard
Copy link
Copy Markdown
Owner

nibzard commented May 28, 2026

Thank you for this contribution! Your implementation was reviewed as part of a batch review of all incoming provider PRs.

We've decided to take a different approach: instead of merging individual provider PRs (which all targeted a different code architecture than what exists on main), we've refactored the entire codebase into a proper provider plugin architecture with auto-discovery and shared mixins. Your provider's API integration patterns were used as reference when building the Lemonfox provider in the new architecture.

The refactor is on branch feat/provider-plugin-architecture and includes 29 providers, 176 tests, and a clean plugin system. We appreciate your contribution — it helped shape the final design. Closing this in favor of the unified approach.

@nibzard nibzard closed this May 28, 2026
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.

2 participants