Comments (3)
This is on my radar, as well as adding semantic versioning. I didn't want to do it just yet to avoid diverging too much from the original repository. Besides, I think there'd be too many breaking changes initially with some of the features I want to add, so it might make sense to just release it as v2 or a separate project when we get around to adding this.
from openapi-ts.
This is on my radar, as well as adding semantic versioning. I didn't want to do it just yet to avoid diverging too much from the original repository. Besides, I think there'd be too many breaking changes initially with some of the features I want to add, so it might make sense to just release it as v2 or a separate project when we get around to adding this.
Ya, the version is still < 1 so we could continue to have breaking changes in minor version until 1.0.0 is released
from openapi-ts.
Oh yeah sorry, meant v1. I suspect that despite this project being pre-v1, many people might be already depending on it, and making sweeping changes might not be easy to migrate, hence the hesitation on my part
from openapi-ts.
Related Issues (20)
- Use exported enums in type fields HOT 3
- It does not pickup typescript in monorepo environment w/ pnpm HOT 3
- Content type headers not passed onto request HOT 4
- Rename conflicting TypeScript identifiers
- DeprecationWarning: fs.Stats constructor is deprecated HOT 3
- export eslint.rules for external usage HOT 3
- Got client HOT 17
- Non-global clients/configs HOT 6
- Export services as module instead of class to enable tree shaking. HOT 10
- Unused @ts-expect-error comment HOT 17
- Support for exactOptionalPropertyTypes in tsconfig.json HOT 3
- Validate response against openapi schema HOT 1
- Standalone package for your client HOT 1
- [question] How does this package compare to `openapi-typescript`? HOT 2
- can't generate a node16 moduleResolution compatible package HOT 8
- Improve support for `Accept` and `Content-Type` headers
- Newly exported `DefaultService` does not exist HOT 14
- Export `FetchClient` interface
- Parameters with `in: header` cause incompatible types HOT 4
- fetch client: snake_case path arguments get converted to camelCase in types, but not in template string HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from openapi-ts.