rafaeltonholo/svg-to-compose

Use case / problem Users want to specify a direct URL to an SVG file and have it automatically downloaded and converted to Compose ImageVector code, without manually downloading the file into a local directory first. Proposed solution Implement the SourceResolver for RemoteSource.Url in svg-to-compose-remote's commonMain. Flow RemoteSource.Url("https://cdn.example.com/icon.svg") -> HTTP GET via HttpTransport -> validate response (status, optional Content-Type check) -> save .svg to outputDir -> return List<Path> containing the single file path Implementation details Uses HttpTransport (#268) for the HTTP request Saves the downloaded file to the provided outputDir using Okio File name is derived from the URL path (last segment), falling back to a hash-based name if the URL has no clear file name Validates the response status code (2xx = success, otherwise throw with descriptive error) Content-Type check is best-effort - log a warning if unexpected but do not fail Returns a Lis

Use case / problem The remote sources feature (#264) needs an HTTP client to download SVG files, ZIP archives, and font files. The client must work across all KMP targets, but using Ktor on JVM is problematic because its coroutine dependency conflicts with Gradle's bundled Kotlin runtime. Proposed solution Implement an HttpTransport expect/actual interface in svg-to-compose-remote with platform-specific implementations. HttpTransport interface (commonMain) interface HttpTransport { fun get(url: String, headers: Map<String, String> = emptyMap()): HttpResponse fun head(url: String, headers: Map<String, String> = emptyMap()): HttpResponse } data class HttpResponse( val status: Int, val headers: Map<String, List<String>>, val body: ByteArray, ) Platform implementations Target Library Notes jvmMain OkHttp Synchronous API, no coroutine dependency nativeMain Ktor CIO engine, coroutines OK on native jsMain Ktor JS engine Retry logic (commonMain) Shared retry

Use case / problem The remote sources feature (#264) needs a common abstraction that represents different types of remote inputs (URLs, ZIPs, fonts) and a resolver that normalizes them into outputs the existing core pipeline can process. Proposed solution Implement the RemoteSource sealed hierarchy, SourceResolver interface, ResolvedSource sealed result, and ZipExtractor expect/actual in svg-to-compose-remote's source sets. RemoteSource sealed hierarchy sealed interface RemoteSource { /** Single SVG file at a URL. */ data class Url(val url: String) : RemoteSource /** ZIP archive containing SVG/XML files. */ data class Archive(val url: String) : RemoteSource /** Font icon library with CSS-based glyph mapping. */ sealed interface Font : RemoteSource { /** CSS file that contains @font-face and glyph class rules. */ data class Css(val cssUrl: String) : Font /** Font file + separate mapping file. */ data class FileWithMapping(