Is your feature request related to a problem? Please describe the problem.
Summary
Kiota's Ruby target (generation, abstractions: preview; JSON serialization,
auth: done; HTTP: preview) is close to usable but marked "not actively worked
on internally" per the Ruby tracking project. I'd like to take it from preview
to stable, motivated by generating a production Ruby SDK for the Open Payments
API (openpayments.dev, JSON only ,so FORM/MULTIPART/TEXT serialization gaps
#2077/#3032/#1049 aren't blockers for this use case).
This aligns with the Interledger Foundation's SDK Grant program, which lists
Ruby as a high-priority open track :
interledger/Grants wiki: SDK-grant-program
Client library/SDK language
Ruby
Describe the solution you'd like
Proposed approach
Questions for maintainers
- Is there a known list of blocking issues for Ruby preview→stable, beyond
the three serialization gaps already tracked?
- Any existing branch or WIP I should be aware of before starting?
- Open to reviewing a draft PR built against a working Ruby SDK for Open Payments?
Additional context
No response
Is your feature request related to a problem? Please describe the problem.
Summary
Kiota's Ruby target (generation, abstractions: preview; JSON serialization,
auth: done; HTTP: preview) is close to usable but marked "not actively worked
on internally" per the Ruby tracking project. I'd like to take it from preview
to stable, motivated by generating a production Ruby SDK for the Open Payments
API (openpayments.dev, JSON only ,so FORM/MULTIPART/TEXT serialization gaps
#2077/#3032/#1049 aren't blockers for this use case).
This aligns with the Interledger Foundation's SDK Grant program, which lists
Ruby as a high-priority open track :
interledger/Grants wiki: SDK-grant-program
Client library/SDK language
Ruby
Describe the solution you'd like
Proposed approach
current preview generator; catalog every failure/bug encountered
test environment (auth.interledger-test.dev)
the bar set by Go/Python/PHP
Questions for maintainers
the three serialization gaps already tracked?
Additional context
No response