feat: Migrate to API contract usage #1111
Conversation
| pathResolver: () => '/users', | ||
| description: 'Create user', | ||
| }) | ||
|
|
There was a problem hiding this comment.
@ilya-levin-lokalise Does storing contract next to controller/route make sense to you, or you would put them into separate files, e. g. contract closer to schemas?
There was a problem hiding this comment.
I know it is not a question for me, so sorry for jumping in 😓
Just to share my 2 cents, in my opinion, and ideally, we will have a package with the client for the service, and the schemas and API contracts should live there so we make sure both are always in sync. Wondering if we should prepare the template with that structure 🤔. Although, this can be done in a separate PR
There was a problem hiding this comment.
but I think you are right, we should optimize for the use-case of reusing the contract outside of the service, so it makes sense if the initial structure is built around that idea. thanks, I'll adjust the code
No description provided.