Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move simulator to its own repository #76

Closed
Tracked by #64
kanerogers opened this issue Aug 31, 2021 · 3 comments
Closed
Tracked by #64

Move simulator to its own repository #76

kanerogers opened this issue Aug 31, 2021 · 3 comments
Assignees
Labels
maintenance A maintenance task!

Comments

@kanerogers
Copy link
Collaborator

No description provided.

@kanerogers kanerogers mentioned this issue Aug 31, 2021
33 tasks
@kanerogers kanerogers self-assigned this Aug 31, 2021
@kanerogers kanerogers added the maintenance A maintenance task! label Aug 31, 2021
@kanerogers
Copy link
Collaborator Author

kanerogers commented Sep 3, 2021

I went with a monorepo to begin with, mostly because I'm lazy, rather than any focussed direction. I know bevy for instance is also a monorepo, but I'm not sure if that's the right way to go.

@Ralith @wbrickner what are your views on repository structures?

@Ralith
Copy link
Collaborator

Ralith commented Sep 3, 2021

Highly recommend using a single repository containing a cargo workspace for closely related projects, i.e. those which tend to have interdependent changes.

@kanerogers
Copy link
Collaborator Author

Sold! Closing this issue then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance A maintenance task!
Projects
None yet
Development

No branches or pull requests

2 participants