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

project directory structure #537

Open
mpiroc opened this issue May 8, 2019 · 1 comment
Open

project directory structure #537

mpiroc opened this issue May 8, 2019 · 1 comment

Comments

@mpiroc
Copy link
Contributor

mpiroc commented May 8, 2019

We are not consistent about how we organize our files.

  • Why are some utilities in foo/utilities/, but others in foo/?
  • What's the difference between src/lambda and src/shared? Why is there so much lambda-specific code in src/shared?
  • Why is cloudformation.ts in a separate directory?
    • ✅ Why does it export a namespace, when we don't use namespaces anywhere else?
  • What really belongs in sam/cli? Does anything belong in sam/?
  • Where should test utilities live? i.e. should we separate test/shared/fooUtils.test.ts from test/shared/fooTestUtils.ts?
  • Why is test/ a child of src/ instead of a sibling?
  • etc.

We should design a consistent directory structure, document it in-repo, and apply it.

@awschristou
Copy link
Contributor

Also for consideration:

  • AWS Explorer code should be separated into its own folder

@justinmk3 justinmk3 changed the title Audit directory structure project directory structure Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants