Skip to content

wip: Add AI MANGA publishing connector - #3

Open
negurvulkan wants to merge 4 commits into
mainfrom
feature/api-connector
Open

negurvulkan wants to merge 4 commits into
mainfrom
feature/api-connector

Conversation

@negurvulkan

Copy link
Copy Markdown
Owner

Adds an experimental AI MANGA publishing connector across the app: account-level OAuth connect/disconnect, per-project external ID tracking, a chapter publish flow that renders pages client-side and uploads a manifest+ZIP, and background polling for AI MANGA validation. Also adds the account settings UI, page-grid publish panel, translations, and docs/feature notes for the new workflow. Includes connector registry and tests for auth, publish routing, and package generation.

Adds an experimental AI MANGA publishing connector across the app: account-level OAuth connect/disconnect, per-project external ID tracking, a chapter publish flow that renders pages client-side and uploads a manifest+ZIP, and background polling for AI MANGA validation. Also adds the account settings UI, page-grid publish panel, translations, and docs/feature notes for the new workflow. Includes connector registry and tests for auth, publish routing, and package generation.
Replace the old "paid" access mode with "supporter_only" across client and server code and update translations. Refactor the AI MANGA connector to follow the partner OpenAPI: explicit scopes, manifest builder (slugify, null handling), separate ZIP creation, include package metadata and sha256, best-effort series pre-registration, and improved OAuth redirect handling for the desktop build. Update Electron to inject AI_MANGA_REDIRECT_URI, adjust tests, and extend docs to describe the desktop/shared client-id behavior.
This change tightens AI MANGA publishing by validating supported source-language mappings, page counts/sizes, and immediate-publish access rules before upload. It also tracks each connected AI MANGA account ID to block cross-account publishing of the same project, keys chapter external IDs by volume+chapter instead of volume alone, and updates the client publish flow and status messaging for supported-language filtering and draft validation states.
Export the AI MANGA manifest/ZIP builders so they can be reused outside the publish flow. Add a one-off script that generates a sample manifest and export ZIP using the same packaging logic ComiKumi uses in production, with placeholder cover/pages for partner review submissions.

This branch has not been deployed

No deployments
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.

1 participant