Skip to content

13) TODO

Jump to bottom
Anthony Quintero-Quiroga edited this page May 16, 2017 · 8 revisions

As with any project under time constraints, some good ideas have been left on the back burner while others, though incorporated, could be improved upon. The following features are a good idea to look into to integrating with Emissary:

  • Contact us/Email notification

  • Customer interaction (ie: Intercom.io)

  • Stripe (for payment)

    • Stripe can only be tested on HTTPS, so we could not figure out how to run the application locally.

  • Form Builder (custom forms and changes to the background color isn't saved)

    • Regarding the color picker, consider adding to the Company schema a "color" field which is returned from the API on login. Save it in localStorage and set the background color with Javascript.

  • Custom themes

  • Roles of Employees (an employee admin should be able to add/remove employees whereas a regular employee can't, etc...)

  • Account statuses (subscribed vs unsubscribed)

    • Consider adding fields to the Company schema that are used to control page access

  • Template the Sidebar and Dashboard code

    • use Handlebars to inject a layout html file with all the shared html

  • Settings Breaks Login

    • password must be sent with the request

  • API Authentication

    • the API currently does not need a token for requests, but we do generate a token on the backend for every client. The token is stored in the browser

  • Solve Selenium issue (When deploying and running the Selenium tests, the tests are pointed towards the Heroku URL. This means the Selenium tests are running on the previous deployment and not the current one. Solving this should be related to Sauce Connect, but we could not figure it out in time).

  • Fix bug regarding Firefox (for some reason, trying to log in with Mozilla Firefox 44.0.2 does not work. Logging in with credentials that would work on Google Chrome and Safari will just refresh the page.)

  • Integrate more Selenium tests (Because Selenium Builder currently only works with Firefox, we could not simulate any tests within the application after signing in. This is related to the previous issue where people cannot login with Firefox. Once the login issue with Firefox is resolved, this issue will hopefully be resolved as well.)

Clone this wiki locally