Skip to content
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

refs with . inside, won't be imported correctly to zod schemas #792

Closed
chiptus opened this issue Jan 21, 2024 · 2 comments · Fixed by #796
Closed

refs with . inside, won't be imported correctly to zod schemas #792

chiptus opened this issue Jan 21, 2024 · 2 comments · Fixed by #796
Assignees
Labels
bug Something isn't working

Comments

@chiptus
Copy link
Contributor

chiptus commented Jan 21, 2024

What version of kubb is running?

2.4.0

What platform is your computer?

codesandbox

What version of external packages are you using(@tanstack-query, MSW, React, Vue, ...)

No response

What steps can reproduce the bug?

see codesandbox https://codesandbox.io/p/devbox/kubb-playbox-5g2n53?file=%2Fswagger.yaml%3A81%2C25

you can see that type pet.Pets is converted to PetPets, and in petPetsSchema, the import is not correct

How often does this bug happen?

Every time

What is the expected behavior?

either the import stays correct and the generated type is in ./gen/pet/Pets.ts, or the input should be corrected

Swagger/OpenAPI file?

No response

Additional information

No response

@chiptus chiptus added the bug Something isn't working label Jan 21, 2024
@stijnvanhulle
Copy link
Collaborator

stijnvanhulle commented Jan 21, 2024

@chiptus I will change this so that pet.Pets will be created inside of src/pet/Pets.ts instead of what is happening now(src/pets.ts). All other imports will then use the correct path.

@stijnvanhulle stijnvanhulle self-assigned this Jan 21, 2024
@chiptus
Copy link
Contributor Author

chiptus commented Jan 21, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants