-
-
Notifications
You must be signed in to change notification settings - Fork 273
feat: Add draft angular-query-experimental support #1218
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
Conversation
|
|
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
mrlubos
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wow, appreciate the effort @max-scopp! I think you'll want to update snapshots with pnpm openapi-ts test:update, the rest looks good to me. We can coordinate on documentation and examples on Discord if you want?
|
I just got myself a glass of rum to celebrate! I haven't found a discord server link, but you can find me under "maxscopp" on Discord and we can discuss the rest. Thanks for the insanely fast response! |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #1218 +/- ##
==========================================
+ Coverage 73.15% 73.19% +0.03%
==========================================
Files 125 127 +2
Lines 17662 17706 +44
Branches 1732 1732
==========================================
+ Hits 12921 12960 +39
- Misses 4738 4743 +5
Partials 3 3
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
Closes #1072
This PR introduces preliminary support for Angular Query Experimental, functioning similarly to the existing React Query plugin.
Reasoning
We’re exploring ways to integrate @hey-api at work, but legacy Angular support is a significant barrier. This PR aims to offer an initial foundation for community collaboration and feedback. While this topic isn’t on a fast-tracked timeline internally, the basic implementation here is meant to initiate development in this direction.
Next Steps
I'm happy to extend examples and provide continued support for this PR, with the ultimate goal of making it merge-ready. The hope is that this initial setup can evolve with community input, building Angular support that meets the needs of various projects.