-
-
Notifications
You must be signed in to change notification settings - Fork 412
feat: add immutable types #1350
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
base: main
Are you sure you want to change the base?
Conversation
🦋 Changeset detectedLatest commit: 8689c2d The changes in this PR will be included in the next version bump. This PR includes changesets to release 1 package
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@smorimoto I'm a little bit unsure on when to use lodash or not in the lib, seems like there is no clear pattern on when it's applied or not. Do you have time to review the PR? |
bugbot run |
@smorimoto I fixed the suggestion from cursor |
bugbot run |
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.
In a functional codebase consumers of
swagger-typescript-api
would want to force properties and values to be immutable even if swagger spec does not havereadOnly
property.With this change one can simply add
--make-immutable
or setmakeImmutable
to force immutable types.