Gwaggli
Gwaggli
WWasp-lang
Created by devrim on 8/21/2024 in #🙋questions
Tutorial API implementation doesn't work for me.
@prof_mark No, they should not be passed to the server environment. You need to set them in your different environments manually. This also allows you to define them per environment. If for example you set up a staging/test environment with a different url test.yourawesomeapp.com you would then use this url on your staging server and yourawesomeapp.com on your production server. Similar with other keys you might want to differentiate between environments. And regarding the fly deploy command: At some point you will want to setup some sort of CI/CD, where the deployment is triggered by for example github actions. So your local .env file would be lost anyways.
30 replies
WWasp-lang
Created by devrim on 8/21/2024 in #🙋questions
Tutorial API implementation doesn't work for me.
I am not using google oAuth so not sure, but seems like you are missing some env variables? Does it work locally, right? Did you set the env variables in fly.io as well? Personal/Videoupdate-server/Secrets? (https://fly.io/apps/videoupdate-server/secrets)
30 replies
WWasp-lang
Created by devrim on 8/21/2024 in #🙋questions
Tutorial API implementation doesn't work for me.
If you used the standard wasp config and deployed it to fly.io your backend server address will look probably something like this: https://<yourAppname>-server.fly.dev So for example: https://devrim-server.fly.dev/api
30 replies
WWasp-lang
Created by devrim on 8/21/2024 in #🙋questions
Tutorial API implementation doesn't work for me.
Depends where you deploy your backend. The API is part of your backend server. So you need to use the url of your backend server.
30 replies
WWasp-lang
Created by Gwaggli on 8/17/2024 in #🙋questions
Custom Type Declarations
@sodic https://github.com/Brakeable/wasp-custom-typings-example Here you go! Steps to reproduce: 1. wasp build 2. cd .wasp/build/web-app && npm run build This fails because of the missing typing while wasp start works just fine When you then uncomment the import import from 'mui' line in the MainPage.tsx file and retry the steps above, the build progresses further and spits out another error, but the missing typing error is gone. (sorry would need to investigate further what that other error means and how to fix it)
10 replies
WWasp-lang
Created by Gwaggli on 8/17/2024 in #🙋questions
Custom Type Declarations
Yeah sure, i will setup an example soon! But probably it will be resolved with the custom tsconfig file that is planned for the next release, right?
10 replies
WWasp-lang
Created by Gwaggli on 8/17/2024 in #🙋questions
Custom Type Declarations
Alright, I could workaround this by importing my mui.ts file in my root component and there force typescript to pick it up. I guess a cleaner solution is dependent on the issue Kapa mentioned?
10 replies
WWasp-lang
Created by Ricardo Batista on 7/18/2024 in #🙋questions
Undefined identifier: User
Hm somehow my answer seems to got lost. Sorry. I was able to single out the error in a sandbox and then resolve it. Thank you anyways! It was indeed a Typescript error that was let through before the update and caught with it.
31 replies
WWasp-lang
Created by Ricardo Batista on 7/18/2024 in #🙋questions
Undefined identifier: User
@martinsos I need to check back when I am at the Computer, but they were similar to the ones Ricardo posted. A mismatch between my Types and Payload.
server/operations/actions/index.ts(161,14): error TS2322: Type '(args: unknown, context: { user: AuthUser; }) => Promise<Payload>' is not assignable to type '(args: MyParamsRype, context: { user: AuthUser; }) => Promise<MyResponseType>'.
Type 'Promise<Payload>' is not assignable to type 'Promise<MyResponseType>'.
Type 'Payload' is not assignable to type 'MyResponseType'.
Type 'string' is not assignable to type 'MyResponseType'.
server/operations/actions/index.ts(161,14): error TS2322: Type '(args: unknown, context: { user: AuthUser; }) => Promise<Payload>' is not assignable to type '(args: MyParamsRype, context: { user: AuthUser; }) => Promise<MyResponseType>'.
Type 'Promise<Payload>' is not assignable to type 'Promise<MyResponseType>'.
Type 'Payload' is not assignable to type 'MyResponseType'.
Type 'string' is not assignable to type 'MyResponseType'.
31 replies
WWasp-lang
Created by Ricardo Batista on 7/18/2024 in #🙋questions
Undefined identifier: User
@Ricardo Batista Did you find a solution for your TypeScript errors? I just got the same after following the Migration being stuck at the migrate-dev command as it can't build the application.
31 replies
WWasp-lang
Created by Gwaggli on 3/18/2024 in #🙋questions
wasp db reset showing help instructions
@ssor_eth I just added a delete function at the beginning which removed all entities and then (when you define the ids in your seed, also reset the sequences:
const deleteAll = async (prisma: PrismaClient) => {
await prisma.entity1.deleteMany({})
await prisma.entity2.deleteMany({})
await prisma.entity3.deleteMany({})
await prisma.entity4.deleteMany({})
...
console.log('deleted all')
}
const deleteAll = async (prisma: PrismaClient) => {
await prisma.entity1.deleteMany({})
await prisma.entity2.deleteMany({})
await prisma.entity3.deleteMany({})
await prisma.entity4.deleteMany({})
...
console.log('deleted all')
}
And the sequence resetting: (a bit ugly i need to admit - open for suggestions here :D)
const resetSequences = async (prisma: PrismaClient) => {
await prisma.$queryRaw`SELECT setval('"Entity1_id_seq"', (SELECT MAX(id) FROM "Entity1"));`
await prisma.$queryRaw`SELECT setval('"Entity2_id_seq"', (SELECT MAX(id) FROM "Entity2"));`
await prisma.$queryRaw`SELECT setval('"Entity3_id_seq"', (SELECT MAX(id) FROM "Entity3"));`

console.log('sequences reset')
}
const resetSequences = async (prisma: PrismaClient) => {
await prisma.$queryRaw`SELECT setval('"Entity1_id_seq"', (SELECT MAX(id) FROM "Entity1"));`
await prisma.$queryRaw`SELECT setval('"Entity2_id_seq"', (SELECT MAX(id) FROM "Entity2"));`
await prisma.$queryRaw`SELECT setval('"Entity3_id_seq"', (SELECT MAX(id) FROM "Entity3"));`

console.log('sequences reset')
}
16 replies
WWasp-lang
Created by mindreaderlupoDO on 4/12/2024 in #🙋questions
Problems in action.ts
Could this be related to the fix by @sodic ? Maybe upgrading to v0.13.2 helps @mindreaderlupoDO Reference: https://discord.com/channels/686873244791210014/1227500285572808755/1228024748429152419
12 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Great news, thank you so much!
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Great, thanks! I am not developing atm so I dont need this workaround but thank you anyways! didn't know about jq. Thanks for the help. Much appreciated 🙂
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Hahaha yeah fair, but still. Nice job and greatly appreciate the help and insane speed 😄
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Your fix did the job for me 👍
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Damn you're a machine! 😄
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
Haha thank you! Let me know if I can be of any Help 🙂
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
I now see, that the import resolving was never the issue (this was TS Server dependent) and also works in my real app. But the type inference in the methods parameters does not work in either.
39 replies
WWasp-lang
Created by Gwaggli on 4/10/2024 in #🙋questions
tsconfig update for v0.13.1
No description
39 replies