jonpitch / danger-brewing Goto Github PK

create a card component for a beer.

As a consumer of delicious beverages from the danger-brewing kegerator, I want to know what beers on tap are homebrew and which are commercial.

Display basic statistics about danger-brewing-hub:

• temperature
• humidity
• is air circulating?
• last line cleaning

Test functionality around adding beers, which uses paper-select from ember-paper. The select menu is rendered in a wormhole; this was problematic to find with ember-cli-page-object a few versions back.

Taps are free-form entry, it would be ideal to have them configured, update add-beer to only allow existing taps, etc.

Track beers data over time, some kind of graphing UI.

Track pours, visualize how much is left, etc. also:

• hub last activity
• beer last poured
• on add-beer, prevent tap that's in use

• Logo
• Favicon

ember-paper in its alpha state is fairly buggy and inconsistent. Evaluate sticking with it or moving on.

• analysis
• clean up existing ui, form validations
• liquid-fire

Clean up jscsrc linting and update all dependencies. Get to Ember 2.10.0.

Update documentation for getting started, integrating with Hub, etc.

When merging to master, using Travis' after_success to push to Heroku.

Basic content, GitHub link, Medium links, etc.

Ember Fastboot support

Right now the hub has a fixed set of supported sensors. Consider the following:

• Allow users to build their own hubs with whatever hardware they want
• Can sensors be added on the hardware side and create themselves in firebase?
• Should flow meters be sensors instead of taps?

Record when line(s) were last cleaned.

• Bring in ember-cli-page-object.
• Establish ground work, mock Firebase, Torii
• Form validation
• Mock Firebase auth
• admin specific functionality

Consider integrating with Untappd, Open Beer Database, etc, to allow for kegs of beer from known breweries, pull in their data, label, etc.