Closed perkinsjr closed 3 months ago
Hey, Can I take this issue ?
Sure @dhawalpatil200 assigning to you now.
Do we have to provide warning to user in form of Snackbar/Toast OR in any other way before creating API with already existing name ?
This is exactly what this issue is.
We have Ui components either alert / toast you can find all of them here.
apps/web/components/ui
Heyy, I'm doing local setup In documentation doesn't understand where to edit this variable. Could you please help me with this? Also I don't understand what is value of host here DRIZZLE_DATABASE_URL='mysql://{user}:{password}@{host}/unkey?ssl={"rejectUnauthorized":true}'
Host would be the planetscale URL for example aws.connect.psdb.cloud
I have followed the steps to setup Drizzle schema. I'm getting following error
Error: VT10001: foreign key constraints are not allowed
oh good catch, you need to enable foreign keys in your db
Heyyy, export TENANT_ID={clerk org id from previous step} I'm not able to understant this clerk org id Could you please describe it briefly about org id and what value should go in TENANT_ID ?
Also pnpm bootstrap is not working Its giving error : ERR_PNPM_RECURSIVE_EXEC_FIRST_FAIL Command "bootstrap" not found
You can use your user id from clerk, or create an organisation and use it's id (=orgId)
double check if you're in the root, cause that script definitely exists :)
In getting started guide it is stated that, UNKEY_KEY_AUTH_ID (which is generated after pnpm bootstrap) should be pasted in apps/agent/.env But there is no agent directory in apps. Is this any documentation issue or I'm interpreting it wrong.
should be apps/api/.dev.vars
I'll fix it
this is only necessary if you plan to work on the API though.
Heyy, I have created api name with 'test' and then again tried to create api with same name it displayed following result. Let me know whether is it good or anything extra can be done.
Looks good, maybe I'm missing something but the PR does not seem to reflect that yet?
You can review PR now. Required changes are present now
Our API name field for both creation and updating doesn't warn the user that they have a API with the same name.
We only need to enforce this in the workspace they are currently in. We don't need to enforce uniqueness because
This needs to be implemented the UI.