At the time of writing, this project is in it's early stages.
Please feel free to provide feedback or start discussions.
Functions should be small.
Smaller than that.
Tests should not have external dependencies. We want the test to run fast in order to give quick feedback to developers.
Try to take advantage of TDD and "red, green, refactor" principals. That is,
- write a test
- make it pass
- write some code until the test fails
- write more test until it passes
- write more code until the test fails
As we build things out, we might not know all the parts that are needed.
Take advantage of golang's interfaces to connect things at different levels of abstractions. This will allow us to build in a very modular way.
With interfaces, we can build systems without knowing the complete details of their implementations.
i.e. define the signature of an interface and we can implement it later however we like.
At the time of writing this, I've built a few "in_memory" datastores that will probably be replaced by database methods later.
If it's in the main branch, it should be able to run. You can make branches, but ideally, they shouldn't live long.
Eventually we will hook this up to automatically deploy (after running tests) the main branch on every commit.
Try to follow idiomatic go where possible. It helps if you download and use the go-tools.
Open to ideas on what to do for a UI. Please reach out or start making commits!
We did have some good experiences using lit-element in one of our other projects though. It was very similar to using something like react. memberdashboard