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

Point out and describe usage of Client shim file #2554

Open
1 task done
Inoir opened this issue Dec 6, 2022 · 0 comments
Open
1 task done

Point out and describe usage of Client shim file #2554

Inoir opened this issue Dec 6, 2022 · 0 comments

Comments

@Inoir
Copy link

Inoir commented Dec 6, 2022

Is there an existing issue that is already proposing this?

  • I have searched the existing issues

Is your feature request related to a problem? Please describe it

So there is a solution how to use swagger and/graphql on client side, but i didnt find any mention about this in the documentation.
Since i found alot issues (i opened also one) for the same problem, maybe its worth it to mention the shim and how to use it in the documentation and avoid more issues about this already solved problem.

Only description i found was in the graphql shim, not even in the swagger shim or on documentation. If you dont know it exists, you dont search for.

Describe the solution you'd like

Add a point into the documentation and mention there is a client usage solution.

Teachability, documentation, adoption, migration strategy

No response

What is the motivation / use case for changing the behavior?

No changing needed in the behaviour, just describe it in the docs

@Inoir Inoir added the feature label Dec 6, 2022
@kamilmysliwiec kamilmysliwiec transferred this issue from nestjs/swagger Dec 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants