Separate frontend and backend

[fedebabrauskas]

I have a setup where my frontend is separated from my backend (separate repositories).

Since I cannot consume the router/contract from my frontend..

Is it safe to generate types from the Open API spec?

[unnoq]

You can follow this: #205 (comment)

[fedebabrauskas]

Thanks for answering!

Probably exporting my contract as an external package would be easier to use along with the oRPC client 😄

Is it overkill to use oRPC without the end-to-end integration? I'm also looking to construct APIs with Open API support out-of-the-box, and I've found oRPC the simplest and quickest way to implement such APIs right now.

[unnoq]

Thanks @fedebabrauskas. oRPC is very simple - each part works independently, so you don't need to use all of oRPC's features

[RajaARK99]

@unnoq is there any possible way get work with spec.json inteasd of router/contract. Creating the client using Open API Json. So we don't need Hey api.

We already generate the spec.json using scalar so it's possible.

It will helpfull for if front-end and back-end separated.

But the thing is need to generate the document in front-end.

If we achieve this. We can use the any open API specification json with openAPILink.

In this case we don't need to generate the type just use the OpenAPI specification json located in project folder or use the URL.

Its already possible mean pls provide the example.

I am not native speaker pls adjust my English.

[unnoq]

Please use router/contract or use Hey API. If Hey API is not good enough, you can open an issue about that.

[RajaARK99]

Please use router/contract or use Hey API. If Hey API is not good enough, you can open an issue about that.

Creating types using a contract JSON is also not possible?