2 次代码提交 3bb098ca44 ... ef9f5c56b2

作者 SHA1 备注 提交日期
  Tatiana Inama ef9f5c56b2 Update README with live version 4 年之前
  Tatiana Inama 3bb098ca44 Update README with live version 4 年之前
共有 1 个文件被更改,包括 0 次插入1 次删除
  1. 0 1
      README.md

+ 0 - 1
README.md

@@ -14,7 +14,6 @@ For an application like this, my candidates were
 
 So based on this, my two top candidates were Gatsby & Next.js, I decided to go with Next.js because of personal preference :)
 
-as a side note the api doesn have cors configured correctly, so i couldnt query directly from fe, and for the challenge i set up a proxy to bypass this
 Aside from my reasons of choosing Next.js, I ended up creating a proxy for the API, since every request from a client application to `https://prisma-fe-dev-assignent.vercel.app/api/` was blocked by CORS policy (this was a workaround to get the API working).
 
 I added the option to choose between the original API or the proxy: adding the env variable `NEXT_PUBLIC_API=https://prisma-fe-dev-assignent.vercel.app/api` would make the client application to use the original backend instead of using proxy.