Skip to content

Add async worker for populating DB #45

@rashadg1030

Description

@rashadg1030

I was wondering if it is a good time to work on the async worker that will populate our DB? Once we get a better idea of the data we need I guess. I've implemented an endpoint for our server that touches the DB and everything, so I think this would be a good next step. And one thing about file structure. We have a file that holds the GitHub query functions on the path src/IW/Server/Search.hs. Is it fine if it goes into the Server folder like it is now, or should it go to another folder called Async or Worker. For example, it could be src/IW/Worker/Search.hs. I'm not sure because technically Search.hs does function on the server, but I think files in src/IW/Server should be related to the issue-wanted API.

Metadata

Metadata

Assignees

Labels

githubSynchronization with GitHub, parsing content from GitHub

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions