Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

AOT compatibility #2967

Open
cacowen opened this issue Sep 10, 2024 · 1 comment
Open

AOT compatibility #2967

cacowen opened this issue Sep 10, 2024 · 1 comment

Comments

@cacowen
Copy link

cacowen commented Sep 10, 2024

Is your feature request related to a problem? Please describe.

Currently the workflow to capture Webhooks and other models depends on direct JSON transformations and furthermore relies on Newtonsoft. These add a lot of overhead in my otherwise simple Lambda function. And pretty much eliminates the AOT benefits.

Describe the solution you'd like

I would like to be able to use stripe-dotnet in a .Net 8 AOT AWS Lambda Function without bypassing trimming and other AOT features. It would be nice to have stripe models that do not rely on Newtonsoft and can easily be added to a JSON serializer context.

Describe alternatives you've considered

No response

Additional context

Perhaps I am just using this the wrong way. I have tried to follow examples here and in YouTube (including the Stripe Developers channel). So far, I have not been able to use this in an AOT application in a straightforward and clean way.

@jar-stripe
Copy link
Contributor

Hi @cacowen, thanks for the request! I can definitely see the use case here. We're planning to look into using System.Text.Json as an alternative to Newtonsoft soon, and I suspect we'll have to get thru at least that work before we can try to understand what we need to do to support this. Unfortunately I can't make commitments about prioritization in the future, but we are tracking it. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants