-
Notifications
You must be signed in to change notification settings - Fork 52
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
Merge this repo into proophessor-do #6
Comments
Good idea, much better than having the Domain duplicated between several repositories. |
I had a similar disucssion with @codeliner. This could resolve the problem with the model duplication. |
I thought about this a little bit: Idea: Instead of having one giant repo for all frameworks, it would be the better way to rename the current This way no dedicated installer (is anyone working on this composer plugin already?) would be needed. The specific framework implementations would just require the Downside would be the model been "buried" in down What do you think? |
@mablae this proposal was already under discussion and rejected by most users. reason: the model is part of another repository and this makes adding feature much harder, because you would have to do this in at least 2 repositories. |
I'm working on updating the app to new symfony flex structure and new prooph bundle versions. Once that is done we can start working on this idea. I really like it. |
when we want to merge both repos we should remove all templating and instead work with react + redux and an API-only backend |
Directory structure something like this:
The text was updated successfully, but these errors were encountered: