Skip to content

Split frontend from backend #209

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

Closed
Turbo87 opened this issue Nov 4, 2015 · 3 comments
Closed

Split frontend from backend #209

Turbo87 opened this issue Nov 4, 2015 · 3 comments
Labels

Comments

@Turbo87
Copy link
Member

Turbo87 commented Nov 4, 2015

Would it make sense to split the frontend from the backend code? Right now they are mashed together and luckily Ember does not expect the source code to be in the src folder too, but there is no clean separation.

We could either move both into separate repositories or at least use separate folders with a common README file. Since the API isn't particularly stable yet the second solution might be better although I would prefer the first one in the long term.

@alexcrichton
Copy link
Member

I personally kinda like having all the code in one repo for now (none of it's that big), but being a little more explicitly about what's in what directory would be fine by me (e.g. reorganizing the internal structure)

@Turbo87
Copy link
Member Author

Turbo87 commented Nov 5, 2015

Okay, good to know. I'll take a look into this after #208 is merged.

@carols10cents
Copy link
Member

I think the organization is okay, and this bug has been around for a while, so I'm going to close this. ❤️

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

No branches or pull requests

3 participants