labzero / lunch Goto Github PK

Maybe find a way to augment geosuggest, or add a second search field?

Also weighted by how recent the votes are

Unnecessary.

Total votes in past 4 weeks
Total decisions in past 4 weeks

It appears that Bing crawls causes these errors:

Message: Cannot read property 'place_id' of null
Backtrace:
restaurants.js 20 .(...)
[PROJECT_ROOT]/webpack:/api/restaurants.js:20:in `.'
URL GET https://lunch.labzero.com:443/api/restaurants/97/place_url
Location No Environment specified on cd3c27cff9ea
Browser Mozilla/5.0 (compatible; bingbot/2.0; +http://www.bing.com/bingbot.htm)

You can see the full error report at:
https://app.honeybadger.io/projects/49826/faults/31294673

To remove things tagged "friday", for example.

Ham Background

Pop up a notification in the corner when new votes come in

More importantly, 3000 is busted locally.

Because there are no restaurants, the Redux state of the restaurant list is malformed (i.e. untouched by normalizr). A first-time user would have to refresh the page to see the first restaurant(s) appear.

To rectify any inaccuracies and to reset vote counts.

Create a "Decisions" table that records where we went. Allow only one decision to be recorded every 12 hours.

UI thoughts:

• outlined checkmark next to restaurants that only appears if there is one vote or more present on the page
• tooltip on checkmark: "We went here"
• any logged-in user can click it
• checkmark becomes filled. Yellow?
• outlined, clickable checkmarks still remain on other restaurants
• when an outlined checkmark is clicked, remove all other decisions from the past 12 hours

Does not affect votes. Can be used for sorting (most recent decisions at bottom).

Like Naked Lunch

Shows up as () in Tag Manager.

Tried it once and broke a few things; delve deeper and see what's actually broken.

Change data structures to use Immutable.js to speed up object comparison / filtering / rendering, etc.

Problem with google-map-react.

Since their name hasn't been loaded, a new vote with an unfamiliar ID could potentially cause a rendering error in the vote count tooltip.

Another safeguard against ballot stuffing

Simply scroll to it instead

Depends on #12

Might be possible if autosuggest returns coords.

User names are private, so just show what was voted down/up/etc.

Can resend the same POST request.