Prathmesh010190 commented on issue #149: URL: https://github.com/apache/openserverless/issues/149#issuecomment-4893482254
Hi @sciabarracom , I'd like to take this on. I've put together a first draft of a SvelteKit adapter for OpenServerless, following the same structure as @sveltejs/adapter-node: it builds the app with SvelteKit's platform-agnostic Server, and bridges OpenServerless's web-action invocation protocol (__ow_method, __ow_headers, __ow_path, __ow_query, __ow_body) to/from a standard Request/Response, including base64 handling for binary payloads. Before I open a PR, I wanted to check a few things with you, since you'd know the platform internals better than the public docs show: Binary detection — for request/response bodies, is there an explicit flag on inbound action params (something like __ow_isBase64Encoded) I should key off, or is inferring from Content-Type the right approach here? Package location — would you want this as a package inside this repo (e.g. adapters/svelte-adapter-openserverless), or split into its own repo the way openserverless-runtimes is? Static assets — my current draft just writes build/client to disk and leaves hosting/upload to ops project deploy. Is that the right boundary, or should the adapter do more here? I don't currently have a live OpenServerless cluster to test an end-to-end deploy against — happy to have a maintainer or CI validate that part before merge, or if there's a way to get access to a test cluster I'm glad to do it myself. If this approach sounds right, I'll open a PR with the adapter, a README, and unit tests. Any guidance before I do would save both of us some churn — thanks! Could you assign this issue to me? I'm ready to start right away. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
