Prepare project for multiple binaries #26

Closed

opened 2021-04-15 19:17:02 +02:00 by Jef Roosens · 0 comments

Jef Roosens commented

2021-04-15 19:17:02 +02:00

Owner

The main library should be useable without having rocket as a dependency
Each binary should get its own tests n stuff

Ideally, we should be able to compile each binary with only the bare amount necessary (e.g. the binary for getting the newest streets from Ivago shouldn't have Curseforge code compiled). This does however seem quite complicated to do, as Cargo only allows one library per project, unless we start a workspace.

The project currently only has one binary, namely the main server binary. We will be writing several binaries for doing periodic things, such as querying all the streets from ivago. Therefore, we'll have to revamp the structure a bit. - [ ] The main library should be useable without having rocket as a dependency - [ ] Each binary should get its own tests n stuff Ideally, we should be able to compile each binary with only the bare amount necessary (e.g. the binary for getting the newest streets from Ivago shouldn't have Curseforge code compiled). This does however seem quite complicated to do, as Cargo only allows one library per project, unless we start a workspace.

Jef Roosens added this to the Fej 1.2.0 - Curse of the Forge milestone

2021-04-15 19:17:02 +02:00

Jef Roosens added the

enhancement

label

2021-04-15 19:17:02 +02:00

Jef Roosens self-assigned this

2021-04-15 19:17:02 +02:00

Jef Roosens added this to the Fej 1.2 - Curse of the Forge project

2021-04-15 19:17:03 +02:00

Jef Roosens referenced this issue from a commit

2021-04-15 19:36:58 +02:00