Add Ember frontend - Githubissues

AgileVentures / EventManager

A system for managing events and hangout participation - microservice API and basic UI

0 stars 5 forks source link

Add Ember frontend #29

Open mattlindsey opened 7 years ago

mattlindsey commented 7 years ago

Move rails to 'backend' directory. Move cucumber up to top level 'features' directory. Add starter EmberJS app in 'features' directory.

mattlindsey commented 7 years ago

See https://github.com/roschaefer/rundfunk-mitbestimmen for great example of this directory structure.

mattlindsey commented 7 years ago

@tansaku Now I'm worried about implementing the UI in the same repo as the API. Are you OK with this? It allows cucumber tests to sit on top of both of them and keeps them in sync easer.

tansaku commented 7 years ago

@mattlindsey it's okay for a spike, and it's okay in general - it's just important to be aware of the options.

You can have front end and back end in the same repo, or split them - there are pros and cons to each - think you could list what you think the pros and cons are?

mattlindsey commented 7 years ago

SAME REPO PROS: Easier to acceptance test and maintain sync between UI and API CONS: Hard to split into 3 repos, if that's desired to maintain 'separation'

DIFF REPOS PROS: Maintains 'separation' of duties, tech stacks CONS: Possibly requires 3 repos and api versioning, better stubbing

Any others?

mattlindsey commented 7 years ago

I said '3 repos' above, but would acceptance tests fit into both repos, making it only 2 required?

tansaku commented 7 years ago

my version ...

SAME REPO PROS:

Easier to acceptance test
clear sync between UI and API

CONS:

If we need to split into 3 repos later that is more work
anyone working on the app has to download all parts and have all parts running locally

DIFF REPOS PROS:

Maintains 'separation' of duties, tech stacks CONS:
- Possibly requires 3 repos and api versioning, better stubbing
- requires clearly maintained and versioned API