-
-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
Move code to /src #397
Comments
I don't mind this suggestion, I think it could tidy up folder management. The current setup gives the impression that all these files are needed to create a Parse Server, when in reality it's only a few (which would be contained in I think that a lot of docs would need to updated inline with this change, just to make sure there's no confusion. We are also working on a CLI version to generate an example Parse Server, so this way you only receive files that you need (for example, you would only receive ESLint files if you select ESLint in the CLI config) |
Nice ! So should I open a PR with this first step or we wait for your CLI? |
@mtrezza what are your thoughts? |
Good idea, I think a I assume that includes the |
The important would be to make sure to update links that points to theses files to avoid 404. But if we forget a few links that only mention |
Hi!
What do you think about moving sources to
/src
folder ? I think it could make it more clear for new users what's config VS actual code ?Have a nice day,
Samuel
The text was updated successfully, but these errors were encountered: