as a result of #81, we have the following files that are currently broken:

• tests/integration/components/service-editor-test.js
• tests/unit/controllers/employees/delete-test.js
• tests/unit/controllers/employees/new-test.js
• tests/unit/controllers/my-calendar/appointments/show-test.js
• tests/unit/controllers/services/delete-test.js
• tests/unit/controllers/services/new-test.js
• tests/unit/controllers/services/show-test.js

From what I can see, the majority of the problems is due to testing of async functions; Usually, the following error occurs:

Assertion after the final `assert.async` was resolved

However there are some other minute details as well. Each person who worked on one of these would probably be best to fix the broken tests.

Needed to ensure tables do not become too large as more entries are added

• we have 16ae7e5#diff-bd45ce3e63b90b6cec9a39d9514b1d97R35 this code that changes the model but does not persist it
• need to either: (a) notify the user that the changes are not saved until they press save or (b) call the save() function within the method
• open to other implementations

• waiting on #26

Appointments Side

• add relationships on Ember
• add relationships on Rails
• add necessary service fields to the appointment-editor.js component
• assign a service package to an appointment during appointment creation
• change service package to an appointment during appointment modification
• remove link between services and appointment during appointment deletion

Tests

• modify appointment-editor.js component tests to include services - Ember
• tests for relationships during creation/modification of an Appointment - Ember
• tests for relationships during creation/modification of an Appointment - Rails

• https://github.com/SamSaffron/message_bus
• service works
• second half of class

• was a result of collision from bootstrap 3 and bootstrap 4

• currently the deployment is manual
• automate the process

The email attribute for employees was not removed in the seeding database file

• we don't have experience with this
• we told the client we aren't sure if this would be done but we would look into it if we had time
• if this is possible this would probably need to be done via back end
• probably need to have a separate process that is just responsible for this
• purpose of this: notification for upcoming appointments (30 min before)

The manage sub-menu does not close after being opened. It only closes when another tab, outside of the submenu is selected.

• we current run Rails tests
• the plan is to keep running only Rails on Travis
• Ember testing will be done locally
• it will be a bit challenging to set up since our repo is private and I currently have 100 free builds per month (I am currently sitting at 51/100)
• from what I understand we need to look into Build Matrix
• found that from here
• if we make our repo public... will be much easier but the code will be public
• I have no problem with running our tests locally for now as long as each developer does their due diligence to run the tests before submitting code

make car_id non optional for appointment
blocked until client and car are created in Ember and linked

Will be used to allow the staff of R & A detailing to log on and perform their desired actions. Should be used to identify whether the staff member is an employee or administrator.

Locally everything works fine.
However, when you want to test it with other devices, rails is not having a good time on mac for some reason. I haven't tested *nix or windows... so...

This is the temporary solution for mac

mac

• type ifconfig and find your ip address (on my machine that is the en0 adapter)
• start your rails server binding to 0.0.0.0 as rails s -b 0.0.0.0
• manually change all references in Ember that references to localhost to the ip you found above. Currently this involves adapters/application.js and authenticators/devise.js files.

There has to be a different way as your ip is most likely to change...

Need to investigate... it seems more of a Rails issue than an Ember issue.

• found that styling is off as result of work on #34
• table does not resize
  
• I suppose this is blocked until I finish #34

• how to install rails (and dependencies)
• how to make it run
• directory structure
• database and what is needed (postgres)
• testing environment vs. development
• production deployment??
• this is NEEDED (for when we hand off project or for someone inspecting the code and not familiar with Rails)

• creating
• deleting
• modifying attrs

• related to appointment-history
• who can view this?
• I think for this one we need clarification:
• can employees see their own appointment history?
• why or why not? (way for them to make sure their payment is correct?)

If you look at the line that begins with Temp: ... it shows the current date that was bound to the start/end datetime-local input fields. For some reason datetime-local is being finicky with our display of date.

A good thing is that we have moment in our project that allows us to display the date in any way that we want. Unfortunately, I haven't had a chance to debug it yet.

From what I understand, it is either a bug in the way that date is formatted... or the binding between the input field and the model's date attribute (which changes start or end into a String rather than keeping it as a Date).

For now, the functionality works if you manually enter everything. Eventually that date input field will be fixed and the Temp: ... line will be removed.

• we are going to assume that id 0 is going to be a default value for every resource (this is so we don't have dangling resources)
• thus, we only send data that is after the first resource
• it is fine for now... will be 2nd semester issue

• Create the template of the customer booking page

• Functionality will be added afterwards

• blocked by #31

Appointments Side

• add relationships on Ember
• add relationships on Rails
• add necessary employee fields to the appointment-editor.js component
• assign a employee to an appointment during appointment creation
• change employee assignment to an appointment during appointment modification
• remove link between employees and appointment during appointment deletion

Tests

• modify appointment-editor.js component tests to include employees - Ember
• tests for relationships during creation/modification of an Appointment - Ember
• tests for relationships during creation/modification of an Appointment - Rails

Research must be performed to determine how to implement a responsive and interactive calendar that will be used to schedule and view bookings.

Functionality

• create
• update
• delete

Tests

• tests in Ember
• tests in Rails

Currently the page is simply a plain form and needs to be updated to conform with the remainder of the site.

• Clean up the my settings page

• Make it more user friendly

• Ensure it is mobile responsive

• add cost (and calculate the initial cost based on the service's cost) #78
• add location (and generate the google image) #98
• change the way appointment start and end times are displayed #78
• - the initial idea is to the follow: (1) pick a date (2) pick start time (2) pick end time

When using the web application in a mobile screen, a hamburger menu can be used to navigate through different pages. Clicking the icon causes the menu to drop-down but it does not close if clicked again

• not necessary to have this console log 16ae7e5#diff-f4c9dea71c1674f594927f9e8d373d4dR21 in Ember/app/controllers/my-calendar/appointments/new.js

ESA should be redirecting to a page on login simply by setting routeAfterAuthentication to a specific route;
However, when I set routeAfterAuthentication: 'my-schedule' it doesn't redirect.
#78

Hola! @Leann88 has created a ZenHub account for the getaclue organization. ZenHub is the only project management tool integrated natively in GitHub – created specifically for fast-moving, software-driven teams.

How do I use ZenHub?

To get set up with ZenHub, all you have to do is download the browser extension and log in with your GitHub account. Once you do, you’ll get access to ZenHub’s complete feature-set immediately.

What can ZenHub do?

ZenHub adds a series of enhancements directly inside the GitHub UI:

• Real-time, customizable task boards for GitHub issues;
• Multi-Repository burndown charts, estimates, and velocity tracking based on GitHub Milestones;
• Personal to-do lists and task prioritization;
• Time-saving shortcuts – like a quick repo switcher, a “Move issue” button, and much more.

Add ZenHub to GitHub

Still curious? See more ZenHub features or read user reviews. This issue was written by your friendly ZenHub bot, posted by request from @Leann88.

• complete when #59 is finished
• which services are required
• which services' API are required

• related to my-account view
• user can modify their own parameters

Ember

• show view
• show logic
• show tests
• update view
• update logic
• update testing
• create view
• create logic
• create tests
• delete view
• delete logic
• delete tests

Rails

• show logic
• show tests
• update logic
• update testing
• create logic
• create tests
• delete logic
• delete tests

• how to install ember (and dependencies)
• how to make it run
• directory structure
• testing environment vs. development
• production deployment??
• this is NEEDED (for when we hand off project or for someone inspecting the code and not familiar with Ember)

• look into how to make rails and ember production ready
• possibly using heroku for both
• some information here = http://fromrailstoember.com/15-deploy-it/
• a buildpack
• another way is to use Redis
• https://ember-cli.com/user-guide/#deployments
• ???

• Change price_small and price_large to just "price"
• we should be able to calculate the respective price rather than having 2 distinct attributes
• needs changes in Rails + Ember