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

Rename "/app" to "/apps" #37

Closed
svengreb opened this issue Nov 14, 2020 · 0 comments · Fixed by #38
Closed

Rename "/app" to "/apps" #37

svengreb opened this issue Nov 14, 2020 · 0 comments · Fixed by #38

Comments

@svengreb
Copy link
Owner

svengreb commented Nov 14, 2020

Using the majority apps as name for the /app directory conveys a better understanding of the actual use case and makes it more clear that it can contain more than one application in the monorepo layout.
This also aligns with the example in the /web directory documentation and the Yarn/NPM workspace configuration in the package.json file where both using the apps directory.

@svengreb svengreb added this to the Next milestone Nov 14, 2020
@svengreb svengreb self-assigned this Nov 14, 2020
svengreb added a commit that referenced this issue Nov 14, 2020
Using the majority `apps` as name for the `/app` directory [1] conveys a
better understanding of the actual use case and makes it more clear that
it can contain more than one application in the monorepo [2] layout.
This also aligns with the example in the `/web` directory
documentation [3] and the Yarn/NPM workspace configuration in the
`package.json` file [4] where both using the `apps` directory.

[1]: https://github.com/svengreb/tmpl-go/tree/main/app
[2]: https://trunkbaseddevelopment.com/monorepos
[3]: https://github.com/svengreb/tmpl-go/tree/main/web#example
[4]: https://github.com/svengreb/tmpl-go/blob/main/package.json#L24

GH-37
svengreb added a commit that referenced this issue Nov 14, 2020
Using the majority `apps` as name for the `/app` directory [1] conveys a
better understanding of the actual use case and makes it more clear that
it can contain more than one application in the monorepo [2] layout.
This also aligns with the example in the `/web` directory
documentation [3] and the Yarn/NPM workspace configuration in the
`package.json` file [4] where both using the `apps` directory.

[1]: https://github.com/svengreb/tmpl-go/tree/main/app
[2]: https://trunkbaseddevelopment.com/monorepos
[3]: https://github.com/svengreb/tmpl-go/tree/main/web#example
[4]: https://github.com/svengreb/tmpl-go/blob/main/package.json#L24

Closes GH-37
@svengreb svengreb removed their assignment Nov 14, 2020
svengreb added a commit that referenced this issue Nov 14, 2020
Using the majority `apps` as name for the `/app` directory [1] conveys a
better understanding of the actual use case and makes it more clear that
it can contain more than one application in the monorepo [2] layout.
This also aligns with the example in the `/web` directory
documentation [3] and the Yarn/NPM workspace configuration in the
`package.json` file [4] where both using the `apps` directory.

[1]: https://github.com/svengreb/tmpl-go/tree/main/app
[2]: https://trunkbaseddevelopment.com/monorepos
[3]: https://github.com/svengreb/tmpl-go/tree/main/web#example
[4]: https://github.com/svengreb/tmpl-go/blob/main/package.json#L24

Closes GH-37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant