Pinging @oyewoas on this Sequelize topic since that skill was offered in #11

Pinging @oyewoas on this Sequelize topic since that skill was offered in #11

Alright @allella

@allella , I will like to clarify what i am to do, am i meant to work on initializing sequelize with sequelize-ts?? and also please is there a link to the board where tasks have been divided into bits??

@Zeko369 Let me know if you stuck somewhere. We can help you, just ping me on discord or any mods. Also, please resolve merge conflict

@Zeko369 Thanks again for pushing forward with the sequelize / sequelize-ts integration.

Have you had a chance to make the suggested changes and finish your checklist?

This is now critical path. Please let us know if we can do anything to help.

@Zeko369 can you please give me push access so that I can help you out, and help you complete the checklist

Alternatively since this PR is good on its own it could be merged and follow up PRs could be made

Hi, how can I help out? My skills are mainly on DB and backend of systems.

On second thought @Zeko369 any particular reason for the pattern of having initSequelize() generate the sequelize instance vs having it be created and exported as part of the db.ts file since it's synchronous? We'd need to access the sequelize instance in other places e.g. when we want to do transactions

@timmyichen it looks like @vaibhavsingh97 is still showing as requesting changes. @vaibhavsingh97 can you review and approve if this is ready.

Also, the package-lock.json is showing in conflict.

@allella @timmyichen I completely forgot about this PR, I fixes most of the requests, I only have one question. What are we going to do about the seeds?, default sequzelie-cli doesnt work with ts files. I'll try sequelize-cli-typescript. Also the build from master is failing I'll look into it?

@nik-john I dont know how you managed to get the CI pass for #158 , because I just merger master and you had a TS bug that stops it from compiling it on the CI.

<StyledComponentsThemeProvider theme={themeObject}>
  <Fragment>
    <CssBaseline />
    <Component {...pageProps} />
  </Fragment>
</StyledComponentsThemeProvider>

you missed the fragment :)

On second thought @Zeko369 any particular reason for the pattern of having initSequelize() generate the sequelize instance vs having it be created and exported as part of the db.ts file since it's synchronous? We'd need to access the sequelize instance in other places e.g. when we want to do transactions

@Zeko369 what are your thoughts? IMO, we should intitalize the database connection and export the connection to app, so that we can reuse it to query the database.

@all-contributors please add @Zeko369 for code tool

@nik-john

I've put up a pull request to add @Zeko369! 🎉