Why there an extra project between front-end and back-end?

[GeeSuth]

Hello,
I don't know if is this correct to ask here. sorry if it is not the correct place!

I was exploring the repository and I confusing why there is an extra project to receive requests from font-end(WASM)
and sent it to the API

What is the problem with sending directly to API from the WASM project????

[gfoidl]

In this project here it's to showcase the Backends for Frontends pattern.

[davidfowl]

That's right, but I could have merged the Todo API directly into the backend still. I decided to keep it separate because I have future plans to support other front end/full stack frameworks that are not going to be served by the backend Todo.Web.Server.

[GeeSuth]

Thank you All 👍 , @davidfowl I found a lot of things confusing me in this solution. I learned more Thank you

[akhanalcs]

@davidfowl What's wrong with Todo.Web.Server serving client apps? Should the backend serve those client apps? Can you explain it a bit more? Thank you!

[dotnetspark]

@affableashish shared models are usually placed in a separate project. You can even nugetize them.

[teate]

How this could be achieved without the BFF? Just simply putting all the logic that the BFF has into the backend project?

[richp582]

Sort of, yes, but then you'd need to deal with cors potentially since the BFF is not proxying calls to the backend anymore and the Blazor wasm is communicating directly to a different server.