feat/new openapi client support 2
- feat: add support for new version of @heyapi and use fetch client instead of axios
- chore: remove comment
- chore: remove comment
- fix: make sure to remove not relevant props from params
- fix: get data from the client
- fix: get data from the client
- chore: release v1.4.2-beta.1
- fix: add formatters and linters on the queries output as well
- chore: release v1.4.2-beta.2
- chore: release v1.4.2-beta.3
- chore: release v1.4.2-beta.4
- chore: release v1.4.2-beta.5
- chore: release v2.0.0
- adding client support
Coverage Report
| Status | Category | Percentage | Covered / Total |
|---|---|---|---|
| π΄ | Lines | 93.19% (π― 95%) | 2040 / 2189 |
| π΄ | Statements | 93.19% (π― 95%) | 2040 / 2189 |
| π΄ | Functions | 93.61% (π― 95%) | 44 / 47 |
| π΄ | Branches | 79.12% (π― 85%) | 144 / 182 |
File Coverage
| File | Stmts | % Branch | % Funcs | % Lines | Uncovered Lines |
|---|---|---|---|---|---|
| Changed Files | |||||
| src/common.mts | 98.01% | 95.23% | 100% | 98.01% | 47-48, 50-51 |
| src/createExports.mts | 100% | 100% | 100% | 100% | |
| src/createImports.mts | 96.18% | 66.66% | 100% | 96.18% | 20-23, 27 |
| src/createPrefetchOrEnsure.mts | 98.79% | 75% | 100% | 98.79% | 98, 130 |
| src/createSource.mts | 100% | 100% | 100% | 100% | |
| src/createUseMutation.mts | 98.78% | 71.42% | 100% | 98.78% | 84, 184, 214 |
| src/createUseQuery.mts | 84.36% | 63.46% | 100% | 84.36% | 80-81, 249, 251-254, 274-286, 325, 350, 379, 388-403, 423-435, 445, 543-552, 558, 648, 665-710 |
| src/format.mts | 89.58% | 80% | 50% | 89.58% | 46-51, 86-89 |
| src/generate.mts | 100% | 100% | 100% | 100% | |
| src/service.mts | 86.27% | 65% | 100% | 86.27% | 35-36, 39-40, 42-43, 46-47, 52-53, 57-58, 66-67 |
npm publish
@seriouslag Do you recall how my commits got here? I am blanking here :P
@seriouslag @omridevk Thank you for updating the client and making the necessary changes accordingly. I apologize for the delayed response. Since itβs not good to leave this unattended for too long, I will resolve the conflicts on my end, release it, and see how it is going in the real world.
I'll merge this for now and manage it in the v2 branch. Since there are still tests to be added and some issues that need to be addressed, I plan to release it once everything is completed.