-
-
Notifications
You must be signed in to change notification settings - Fork 3k
chore: document core/infra architecture #14815
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
base: main
Are you sure you want to change the base?
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Here's my honest feedback:
- the coding example isn't concrete. You mixed different code, which makes it very difficult to understand how everything is mixed together. We start with the key and logger, but then there's no logger anymore, we eventually end up showing some helpers. This doesn't help understanding how the whole code fits together
- we start with business logic and infrastructure, but then I don't know where the business logic is anymore
- we don't show how the final usage would look like
- we don't show what the final testing would look like, and what we should test. We mentioned only what we shouldn't
- overall there are many assumptions, and even after reading this multiple times, I still can't understand why some interfaces are in
domain.ts, while others are indefinitions/ - overall, don't be afraid to be a bit more verbose, and since you rely more on the code example, make sure to make it consistent and good
|
Thanks for the feedback! I wasn't sure how detailed it should be, I will make it clearer 👍 |
Well, you're imparting some knowledge to the team and current/future contributors. I believe we should be detailed enough so that even first-time contributors understand how the project works |
|
To be clear what I'm proposing here will very likely evolve as we go, this should be considered a living document/guide |
Changes