-
Notifications
You must be signed in to change notification settings - Fork 374
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
Add ARCHITECTURE.md file #942
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.
Thank you for doing this! I'm trying to think through how exactly to do this but we probably want to further tease apart the auto-genned resource commands (and how they work) with non-API commands (like listen, status, etc).
Probably also worth explaining how configs and plugins work, but that's for us and not you/this PR.
Ok, I've tweaked the language based on feedback- it's hopefully more clear now! |
updated per your comments- thank you! |
Reviewers
r?
cc @stripe/developer-products
Summary
After reading through the code, add an ARCHITECTURE file, outlining the general structure of the codebase and hottest code paths. This was mostly meant as an exercise for myself, but I've found it helpful to save and maintain these documents over time.
Also, I haven't done much work in this codebase, so please double check that what I wrote is accurate and helpful! Also, feel free to suggest other important sections that a new contributor would find helpful when diving into an unfamiliar codebase.