W
Wasp•2mo ago
mb23

Importing functions to worker files

I'm having a hard time importing functions to my worker files. Not sure what I'm doing wrong here 😄 How can I use functions from my actions.ts and queries.ts in my workers?
4 Replies
kapa.ai
kapa.ai•2mo ago
Hi @mb23. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
MEE6
MEE6•2mo ago
Wohooo @mb23, you just became a Waspeteer level 5!
kapa.ai
kapa.ai•2mo ago
---------------------- Based on the knowledge sources provided, it appears that using actions and queries directly inside worker files in Wasp is not straightforward and may not be fully supported in the current version. However, I can provide some insights and alternative approaches: 1. Direct usage of actions in workers: According to the Discord support thread, trying to use actions inside workers can lead to context-related issues. Actions typically expect a context object, which includes user information, but this context is not naturally available in worker environments. 2. Alternative approach: Instead of directly importing and using actions or queries in your worker files, a recommended approach is to create separate functions that contain the core logic you want to reuse. As suggested in the Discord thread: "If there was logic in the action you wanted to reuse from Job, what I would do in this case is create a function for that logic, normal JS function somewhere in your server code, I would call it function X, and then your action can call call that function X inside it, and also your job can call that same function X. That way you can share a lot of logic, as much as you want." 3. Worker function structure: When implementing a worker function, you can follow this structure as shown in the Jobs documentation: 
export const foo: MySpecialJob<Input, Output> = async ({ name }, context) => {
  console.log(`Hello ${name}!`)
  const tasks = await context.entities.Task.findMany({})
  return { tasks }
}
export const foo: MySpecialJob<Input, Output> = async ({ name }, context) => {
  console.log(`Hello ${name}!`)
  const tasks = await context.entities.Task.findMany({})
  return { tasks }
}
This worker function receives args and a context object, which includes the entities you specified in the job declaration. 4. Updating client UI from workers: If your goal is to update the client UI based on changes made in a worker, you might need to use WebSockets. Wasp provides some support for WebSockets, which you can use to send messages from the server to the client and update the UI accordingly. In conclusion, while directly importing actions and queries into worker files may not be straightforward, you can achieve similar functionality by restructuring your code to share logic between actions, queries, and workers using common functions. For real-time updates to the client, consider using WebSockets. If you need more specific guidance, you might want to share your current code structure and explain what exactly you're trying to achieve with these imports in your worker files. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ---------------------- Sorry @mb23, I seem to be having a bit of trouble. Don't worry though, I've pinged my support and they will try to fix me up! :technologist: Perhaps try again in 15mins?
miho
miho•2mo ago
Could you provide us with some code examples so we can maybe reproduce the problem?

Did you find this page helpful?